It's worth noting that there have been reports of performance degradation running VMWare alongside Hyper-V[0]. Don't get me wrong, I love what Microsoft is doing with Windows Hypervisor Platform (WHP/WHPX). There's even experimental support for running accelerated QEMU VMs on Windows Hosts[1]. Hopefully these performance issues improve over time.
I know WSL2 only requires a part of Hyper-V to run ("Virtual Machine Platform"). This also allows it to work on Windows Home. I wonder if anti-cheat systems will be able to do there jobs while still allowing WSL2 to be used. I don't know enough about how Hyper-V is used to circumvent anti-cheating.
To expand (I can't edit now)... ESEA anti-cheat is posited as Hyper-V specific, but it's actually against being virtualized in general.
I was able to work around this with KVM on Linux with a GPU passed to a Windows VM.
I tweaked the libvirt XMLs (VM definitions) a few key ways and was able to convince ESEA it's bare metal, but not Valorant. I never got to play it, but it's fine by me :)
This combination works well enough, I only boot up Windows when I need a couple anti-cheats I've managed to trick (that also can't work in Proton)
It's more compatible if you want to access a usb or serial port.
WSL2 is like a car that's great in most ways but for some reason just cannot make right turns from one-way streets. You might not encounter that particular situation very often but your car still needs to be able to do it or else it's just an annoying 3/4-baked thing that is better just skipped until it's actually fully functional.
Especially since there is some feature discrepancy between WSL1 and WSL2, sometimes there is a need to use the former.