Quick follow-up:

1. For some reason the Quake folder that is present in uploaded faulty VM is corrupt (it reports PAK0.PAK error at startup and byte size is 1 byte off). Please use the Quake ZIP I attached yesterday to investigate the issue (or AutoCAD 2023.1.3, which is easier).
2. I tested the faulty VM that I have uploaded yesterday (created by VMware Workstation Pro 16.1.0, VMware Tools is 12.2.0) in VMware Workstation Pro 17.0.0. The Quake game starts (the one that is attached to this post) and the framerate is not ~10 fps but ~30 fps. Still way lower than ~300 fps when run in VM created in VMware Workstation Pro 17 natively. AutoCAD 2023.1.3 does crash (when manipulating any 3D object, i.e. simplest box) without any error dialog, VMware Workstation Pro continues to run after AutoCAD crashes.
3. VM (guest and host OS is Windows 10, version 21H2, 3D accelerated with 2 GB of VRAM) created from scratch in VMware Workstation 17.0.0 and VMware Tools 12.2.0 performs fine, great framerate in Quake (~300 fps in 2560×1600), great performance and no crashes in AutoCAD 2023.1.3.

I have also stumbled upon an ongoing thread regarding ISBRendererComm regression in VMware Workstation Pro 16 that leads to crash similar to the one I experienced with Quake. It appears to me that my initial claim regarding recent AutoCAD version may be connected to this issue in some way despite the absence of error dialog box.

I will be upgrading to VMware Workstation Pro 17.0.0 since it appears to be working fine with my computer. It looks like this is the only option for now. Maybe that is in some way related to my laptop's GPU that was released in summer of 2020 and sports RDNA1 architecture. I'm happy I didn't roll out VMware Workstation Pro 16 to the production environment!

Please let me know if there's something I can do to help you get this issue sorted.