Hardening Brave further - Question

Hello :wave:t4:
I’ve been looking around in the flags of brave and reading a few articles. So as per DivestOS, and general consensus on the web, Chromium Browsers have a strong security feature which is called
Per-site process isolation:
“-is a powerful security feature that seeks to limit exposure of a malicious website/script abusing a security vulnerability.”
So far so good. Not new. But in the flags I went and activated Strict Site Isolation and Strict Origin Isolation.
Idea came from here:

Site Isolation mode: Site Per Process, Strict Origin Isolation, (new) Password Sites, Logged-in Sites.(default)
The question that remains is:
Benefits of strict origin isolation is described here:

Having a hard time understanding the quote from chrome://process-internals:
**“Experimental security mode that strengthens the site isolation policy. Controls whether site isolation should use origins instead of scheme and eTLD+1. **
– Mac, Windows, Linux, ChromeOS, Android, Fuchsia, Lacros”

This is true, but just note that on desktop OSes, Firefox has had this feature for a while too.

Extra read on Fission, Firefox, Gecko, Webview, Chromium.
Just facts (as far as a noob like me can tell), still use Mull alongside Brave: