Obviously it was confirmed by some users, see this thread, with the exception of a Windows VM’s.
The original issue with ESXi refusing by some magic bit they don't even use was fixed, as that bit is now exposed to the VM any other issues are rather different ones – so no, there's no exception for the specific issue of this specific thread. Your problems have very likely a different root cause.
It seems obvious that Proxmox is not interested in the Home Lab market, from your reaction
Yeah, the ten thousand posts of Proxmox staff themselves, plus a huge community on top of that, helping people here does not really make such an observation all too obvious to me..
Anyhow, IMO VMWare Workstation inside Windows VMs is an odd use case for any setup, be it home lab or enterprise, but what's more relevant, it's a few to many layers away from Proxmox VE. There's VMWare that makes the product you got a problem with to ask first, then there's Windows, the platform you want to make the former run on, which also offer support.
The same with the pricing model of the product
The product itself is 100% free, released under the GNU AGPLv3..
as long as the only support answers are not such as this.
Well, you will be asked for details there too, which you did not yet provide and might have made this conversation a bit more productive, but yes, for a paid support you get guaranteed responses for which the quality naturally depends on the support level (basic subscription is basic support) and if the question is covered by the subscription agreement one agrees to when buying said subscription. VMWare workstation is a proprietary project that we have no ties with whatsoever, so enterprise support w.r.t. that will be obviously limited from our side, but as said, you can ask VMWare about their products.
Not if the community forum is not open and inclusive.
Not sure what you're getting at here? Nobody censored you, but nobody here owes you anything either.
While it won't guarantee you an answer in this 100% free of charge forum, providing details asked is surely increasing that chance for getting it more than this route of conversation here.
Ps. The proprietary world is great on checking some bogus details for refusing to run even if they could, so CPU type (that includes some hyperv features that one can enable/disable) and SMBIOS strings that identify the platform could be at "fault" here.
It might also be the case that VMWare Workstation is just not supporting running like this, we did not make it so can't answer that..