Just like you, this is the line I was seeing in an older visual studio when I would debug:
FTH: (18348): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***

If you look back on the trace mine says this:
Loaded 'C:\Windows\SysWOW64\combase.dll', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\rpcrt4.dll', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\setupapi.dll', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\bcrypt.dll', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\mpr.dll', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\sfc.dll', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\winspool.drv', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\SHCore.dll', no matching symbolic information found.
Loaded 'C:\Windows\SysWOW64\sfc_os.dll', no matching symbolic information found.
FTH: (18348): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***

I renamed sfc_os.dll and the performance went up what seemed like an order of magnitude.    This is the only change I made.  Renaming the file can be a bit challenging.  Look for directions to change a file that has TrustedInstaller security, in case the following link dries up in the future:

https://www.lifewire.com/how-to-get-permission-from-trustedinstaller-in-windows-10-4780469

Cheers,
Bob