The webRequestBlocking API exposes fairly low level hooks into the networking stack to the javascript layer which would be a significant limitation to performance optimisation in how requests are processed.

That said I've now read that the API is still available to policy based extensions (essentially OS installed extensions) in manifest v3, so that doesn't hold water since it's literally the same API.