@dlanced ,
Suggestions re New Private Window with Tor
–
Enable the upgrade of navigation to always use HTTPS:

–
Disable “Use Secure DNS”:

(Note: Some say Enable and use one of the Custom providers; but Disable works for my Brave Browser setup.)
–
Go to: brave://settings/getStarted . . . and set new windows to open about:blank
:

–
Go to: brave://net-internals/#dns
and click on Clear host cache
Next, go to: brave://net-internals/#sockets
and click on both (in succession):
Close idle sockets
Flush socket pools
Exit/Quit everything and restart your computer.
–
Notes re what are:
DNS cache:
Socket pool:
With pooling, instead of closing a connection after it is used, we can keep it idle while it waits to handle another request. This saves the resources required to create a new connection.
–
Observe: brave://tor-internals/
–
Locate the cldoidikboihgcjfkhdeidbpclkineef folder and open it:
/home/[username]/.config/BraveSoftware/Brave-Browser/cldoidikboihgcjfkhdeidbpclkineef
Observe the contents of that folder, given the following:
The Tor items therein are supposed to be replaced / updated, when you Disable . . . and wait a moment . . . then Enable the Private window with Tor switch:

And, within
/home/[username]/.config/BraveSoftware/Brave-Browser/tor
some of the files are created, while some are updated, but I am uncertain about which . . . as a result toggling that switch.
I discovered that, AFTER Enabling the Private window with Tor switch, I had to open a New Private Window with Tor . . . and wait . . . until the Tor component showed up.
–
Re Component updating, do not block:
componentupdater.brave.com
go-updater.brave.com
variations.brave.com