So after cooling off a bit the other day, I went for the near-nuclear option and did a clean install of the OS moving to 2004 since the issue exists at 1909 which is where I was anyways. I think I would have to roll back a lot further to avoid it, and there were substantial security enhancements over the last 2 years :P
Doing this cleared most of the problems I was seeing in Event Viewer.
I had a brief scare with Defender Offline Scanner not wanting to launch but it eventually did -- not that it works anyways still with my internal harddrive configuration. This has been broken for 2 years now. But at least it is still broken in the same old way.
The only "new" glitchy thing that I see is within Process Explorer, when running as Admin, there is a weird error text still under the path for Registry and Memory Isolation processes -- but I am beginning to think that is a 2004/process explorer issue.
I can also successfully toggle core isolation on and off at will (at the expense of WdNisSvc running or not). This is likely because whatever other software conflict existed (xtuacpidriver.sys and iocbios2.sys) didn't get reinstalled because I did not reinstall ANY of the OEM bloatware.
So now the "only problem" is that even after the monthly update, Core Isolation and Defender real-time AV don't work at the same time as one another.
As far as I can tell the issue still persists.