The opening of the virtual disk looks fine.
2020-10-31T08:11:52.472-08:00| vmx| I005: DISK: DiskConfigureVirtualSSD: Disk 'scsi0:0' identified as Virtual SSD device.
2020-10-31T08:11:52.472-08:00| vmx| I005: DISK: Opening disks took 3 ms.
It looks like things start to slow from this point onwards in the vmware.log
2020-10-31T08:11:53.913-08:00| svga| I005: SVGA enabling SVGA
2020-10-31T08:11:53.916-08:00| svga| I005: SVGA-ScreenMgr: Screen type changed to RegisterMode
When the SVGA video driver is loaded, over 33 seconds has elapsed from the start of the log. For reference a Windows 10 VM on Fusion 11.5.6/macOS 10.15.7 on a 2014 MBP just under 21 seconds has elapsed at the same point.
2020-10-31T08:11:51.809-08:00| vmx| I005: VTHREAD 4438236608 "vmx" tid 1277757
2020-10-31T08:12:25.105-08:00| vcpu-0| I005: Guest: vm3d: SVGA WDDM Full Display driver, Version: 8.17.02.0001, Build Number: 16772660
2020-10-31T08:12:25.105-08:00| vcpu-0| I005: Guest: vm3d: WDDM OS version: 6.1, build number: 7601, service pack version: 1.0, platform Id: 2, product type: 3, suite mask: 0x112
It might not be a good comparison considering that there could be more services starting up in the Windows Server 2008 R2 VM (if this is a domain controller, DHCP server, or database server, etc) than a Windows 10 VM and add to that there are inherent inefficiencies of an old OS like 2008 R2. You could try to compare this with the other Windows 2008 R2 VM and/or Windows 7 VM and it might be a better comparison than using a Windows 10 2004 VM.
One thing I noticed is that the Hard Disk Buffering is disabled. Try to leave it as "Automatic" in the Advanced settings of the VM.
2020-10-31T08:11:52.242-08:00| vmx| I005: DICT hard-disk.hostBuffer = "disabled"
And try to change the virtual optical drive from IDE to SATA and remove the ISO file reference if it is not needed during the boot up.