(1) Yeah, I think you are an Administrator & even went above & beyond to make a new one; so, it can't be that.
(2) The closest I get to the meaning of 0x80070020 is in here...
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d?redirectedfrom=MSDN
2.2 Win32 Error Codes
"
| 0x00000020<br><br>ERROR_SHARING_VIOLATION |
The process cannot access the file because it is being used by another process. |
"
Sometimes the high-order bits (1st half) in an error message can be ignored. But it's impossible to think what can possibly be using your Registry in the pre-boot environment to prevent Defender from using it. It just doesn't make sense. Well, you aren't running Windows from within a VM (Virtual Machine) -- are you? But I know little about that.
(3) I wasn't totally thorough in my search, but dotomi.com seems to be more of a spy than a virus. Maybe it even causes pop-up ads. I doubt it was the problem, anyway glad you are rid of it. Good going.
(4) OK, you've got a Recovery partition, & it is enabled. MsssWrapper.log does show access to it probably because Defender will use something inside. Maybe Defender, itself, is in there (I don't know). I do know the version of the tools in the Recovery partition should match or exceed the version of Windows that is installed. But I think yours will match because you've done both a reset & a repair-install. To see your version...
(a) Click Power, then Shift+Restart to get to the "Choose an Option" screen.
(b) Click "Troubleshoot > Advanced Options > Command Prompt"
(c) Try this command...
Reg Query **HKLM\SYSTEM <<<**That was the Registry key Defender failed to access. Can you access it?
(d) Close the Command Prompt, & click "Continue" to return to Windows.
At the top of the Command Prompt it shows the Windows version. Here in Windows, mine says...
Microsoft Windows [Version 10.0.19042.867] <<<20H2 fully updated to OS Build ...867
(c) 2020 Microsoft Corporation. All rights reserved.
The OS Build might be lesser in the recovery environment, but that's OK. For me, IIRC, even the version is ...19041... (2004) because I did the mini-upgrade from 2004 to 20H2 through Windows update. That's OK too. You'll likely have ...19042... because you did the reset & that repair-install.
Here was my Reg Query while booted to Windows...
C:\WINDOWS\system32>reg query HKLM\System
HKEY_LOCAL_MACHINE\System\ActivationBroker
HKEY_LOCAL_MACHINE\System\ControlSet001
HKEY_LOCAL_MACHINE\System\DriverDatabase
HKEY_LOCAL_MACHINE\System\HardwareConfig
HKEY_LOCAL_MACHINE\System\Input
HKEY_LOCAL_MACHINE\System\Keyboard Layout
HKEY_LOCAL_MACHINE\System\Maps
HKEY_LOCAL_MACHINE\System\MountedDevices
HKEY_LOCAL_MACHINE\System\ResourceManager
HKEY_LOCAL_MACHINE\System\ResourcePolicyStore
HKEY_LOCAL_MACHINE\System\RNG
HKEY_LOCAL_MACHINE\System\Select
HKEY_LOCAL_MACHINE\System\Setup
HKEY_LOCAL_MACHINE\System\Software
HKEY_LOCAL_MACHINE\System\State
HKEY_LOCAL_MACHINE\System\WaaS
HKEY_LOCAL_MACHINE\System\WPA
HKEY_LOCAL_MACHINE\System\CurrentControlSet