Some of that I've learned so far, it look like starting with Windows 10, version 1607 and Windows Server 2016 the VM Security features of Windows are automatically enabled when the Hyper-V hypervisor is enabled, and when that is enabled other VM systems are unable to run due to security logic in Win10. Further, the Hyper-V hypervisor is running inside a VM, so testing for the Hyper-V hypervisor being enabled and active is looking like what MS is trying to push this situation into being a single, simple setting check for being in a VM or not. More research to follow, which I'll report back here.