@synthesis
I view Brave Shields as something of a chess game.
If a Brave Browser user enables All Shields DOWN, then the browser is effectively using the traditional chess board.
If a Brave Browser user leaves ALL Shields UP and carefully/incrementally adjusts the settings, then the browser uses its special, privacy and security chess board ← that has 2 rows of pawns.
The other side of the chess board, is the website and its servers ← that are expecting your Internet browser to be using a traditional chess board.
Given the Brave principle, that Brave Browser is a Privacy & Security Internet browser (ie not traditional) . . .
The objective is, to only allow the removal of the few chess board pieces that provide enough avenues for the website servers, to do enough of their jobs that provide enough of what Brave Browser needs to render the webpage(s).
Incremental / subtle changes in Brave Shields settings, lead to incremental / subtle differences in website payloads that are sent to the browser.
Thereby, incremental / subtle changes in Brave Shields settings have some control over what the website sends and how the Internet browser reacts.
All Shields DOWN, is akin to removing every row of the Brave Shields chess board pawns.
IF you monitor the Developer Tools window > Network tab:
How to use Developer Tools:
Developer Tools > Network:
. . . while making subtle changes to Brave Shields, you can see the changes in website - to - browser activity.
I test, with the Disable cache
selection, Enabled; and again, with that Disabled.
The point:
Sometimes, dropping all of the castle drawbridges, allows a flood of interrogation and snooping by the website.
Some website developers are throwing everything they can, into the breach; and THAT can stir up trouble, because the website receives an unexpected array, or mess, of info - some delayed for too long (because the website is fussy about the ying-and-yang of to/for data flow) - back from the browser.