rwilsond,
The issue is still here! It has not been fixed (and maybe never will be). Based on my communications with Microsoft, the company remains, even still, unaware of this bug.
You mention "numerous tweaks" you have made. Perhaps you have made some (or all) of these four tweaks that people have tried with varying degrees of success.
1) Placing a load on the GPU. This can be done with programs like FurMark and OCCT. It can, however, lead to system instability as well as heat and other related issues. And it works intermittently, depending on the amount of load and other factors.
2) Setting the CPU affinity to use only one core. Be aware that this adjustment can cause sluggish performance, system errors when multi-tasking, and even Blue Screens.
3) Adding Office programs as games and setting the GPU driver for 'low latency = ultra' or 'anti-lag = enabled'. This works partially well and only with certain drivers. It can also lead to program instability and errors, as well as other strange behaviors (although apparently not Blue Screens).
4) Disallowing CPU core parking. This adjustment, on many systems, makes glitches rare. It is perhaps the most widely effective of these tweaks. It can, however, lead to Blue Screens in certain scenarios, as documented on the Bitsum ParkControl website.
Combining more than one of these tweaks at the same time can result in greater effectiveness (as well as greater instability). Perhaps, rwilsond, you did some of these tweaks simultaneously and found the combination effective. Congratulations.
Even though these temporary workarounds can help to varying degrees, they are of course no substitute for Microsoft actually becoming aware of this bug and fixing it!