Regarding your additional two Qs:
- Windows 10 v2004 Enterprise x64 (Final release; i.e. Build 19041). Only the 2004 release has the support required for Hyper-V interop (excluding Insider builds).
- Right now I'm not sure I'd call it a bug in either. I don't know enough about WDAG to say if keeping locks on those catalog files is expected behaviour, and the VMware Workstation Pro installer presumably just isn't expecting other processes to be maintaining references to those files. Updating the VMware Workstation Pro installer to at least check for this case would likely be the simplest path forward (and updating the release notes), but it's not necessarily a bug, just a system configuration that should be handled.