TL DR don't use M$ as a host for anything. It's mainly geared towards M$ IT networks. HyperV is clearly not a technology with gaming/performance in mind.

Wtf is 'checkpoint' its called a snapshot in literally every other vm literature on earth. The options are scant, basic features are mangled and made M$ specific. The hyperV VM manager looks like a toddler's version of virtualbox. Linux/kvm have far more mature options and doesn't encumber you with unnecessary M$ garbage. I find this kind of behavior typical of m$ which is why I no longer use their OS on baremetal. This is not due to a lack of functionality on amd's part, but microsoft simply refuses to support it. This is microsoft we're talking about remember? For example nested virtualization works perfectly on intel cpus but not amd. Then you further slow things down by then adding the guest vm you wanted and attempt to do gpu passthrough (which I would consider at alpha stage). Your host machine despite having nothing to do with the vm you will create for gaming, will suffer performance impact as it is now a vm itself. Which means your entire host system is now a guest under the hypervisor.

When you enable hyperV in windows, even without running a single vm, your entire windows is now also under hyperV. Best part is you don't have to be beholden to microsoft and their software stack.

With kvm and virtio you can use gpu passthrough with almost bare metal speeds. Both KVM and HyperV are type 1 hypervisors.

Kvm vs vmware vs virtualbox