Then you need to manage custom certificates and embedded browsers and updaters may not handle proxied connections well. (And what about your tv where you can't provide custom CA certs?) This way of handling things never ends well. Both in enterprise solutions and consumer ones.
A lot of ads and sites use complex JS as well, so an extension can lean on the browser's rendering engine to JIT block that stuff..
A proxy that wants to do this before the browser will need to do a lot more work I think?
TLS makes that tricky as you need a MITM proxy.
And cert pinning in the browsers blows this out of the water, which is why I'm of two minds about it as a security feature. It seems that a lot of security these days is really about removing people's control over their own devices.
You can import an own root cert which will be honored. I work in a company where all internal servers have a certificate a non-public root has signed. Works both on Chrome and FF.