I recently saw someone get better benchmark (Futuremark) results with Win10 running in a VM on Linux than native Win10.
I haven't tried this personally yet, but I do intend to.
It was apparently a hassle in the past, but the bypasses are basically built in to the tools now. Nvidia is calling the blocking behavior a "bug", but the have no intention to act on it.
The first is that it's pure, unsubstantiated, guesswork. You'll spend countless hours changing obscure undocumented parameters hoping that things will work. I tried, and it's not a fun thing to do, because you don't learn anything substantial.
Second, this type of operations have a sky-high level of brag factor. People will tell on their blogs/posts that they succeeded in "making XXX work and that it's stable", but they don't tell you that their computer explodes (so to speak) two minutes after they start XXX. Again, I know because I've worked on similar things, and the patterns are the same.
You may be lucky, but if you aren't, it's a lot of time wasted (it always looks like the "final solution" is behind the corner!).
I went for it, and it actually ended being significantly easier and better performing than I expected. I did have to take a few days and learn a bit about qemu, but I'd expect that much.
I will say that older motherboard (perhaps some new ones too) might not have firmware that fully support what's being done here. It's hard to say which, but you can see what people have had success with if you search around (Asus z170a works for me).
This is a little light on details but is a good resource for the steps involved: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVM...