Nojlk
Some links I remember going through:
https://www.qubes-os.org/doc/device-handling-security/#pci-s...
> Additionally, Qubes restricts the config-space a VM may use to communicate with a PCI device. Only whitelisted registers are accessible. However, some devices or applications require full PCI access. In these cases, the whole config-space may be allowed. You’re potentially weakening the device isolation, especially if your system is not equipped with a VT-d Interrupt Remapping unit. This increases the VM’s ability to run a side channel attack and vulnerability to the same. See Xen PCI Passthrough: PV guests and PCI quirks and Software Attacks on Intel VT-d (page 7) for more details.
https://security.stackexchange.com/questions/162122/gpu-pass...
As for the OP, I feel like if somebody cares about security, they shouldn't be doing any of this. Trying to come up with some self-designed hodgepodge of things isn't really enough security-wise, even if you do use VMs, and I'd find it hard to trust something like this as a platform to do anything important on.
There's never going to be a mass exodus to Linux. People have been promising the year of the Linux desktop for as long as Linux has been a thing. It's time to find a way to coexist, and Proton is so far one of the best solutions for gaming.