Deblobbing Qubes

Qubes is a great distro for security; I've been running it for close to two years now with minimal issues. The only thing is that it contains binary blobs. Templates include non-free firmware with them by default, dom0 kernel has blobs, fedora templates have kernel blobs, the whole thing is a non-free mess. I'm trying to run the minimal amount of blobs needed for x86_64, which currently if I were to run a free distro would be limited to coreboot blobs. Unfortunately, blobs in Qubes set me back quite a bit. I'm mostly running qubes with debian and whonix templates as neither of them have kernel blobs. Removing firmware packages is easy, but deblobbing dom0 and fedora template kernels is hard. They're managed by the Qubes project themselves, and simply installing linux-libre kernels doesn't work. Not to mention circumventing dom0's security measures and installing linux-libre kernels would be a security risk. What's the options here? Start rolling my own packages on a 3rd party repo to fix dependency hell with linux-libre? Somehow convince the Qubes devs to allow the option to implement linux-libre kernels in place of fedora kernels?

Since the kernel on the host system does have to detect the hardware to provide it to guests, it's a difficult position to be in. You could also run virt-manager (or VirtualBox) under Trisquel or Debian. Create your own VMs. It won't be as isolated as Qubes (which allows VMs to intercept hardware and network traffic) but it's a start. Is that something that your threat model allows for?