Which doesn't make a whole lot of sense because you can run all the Chrome components in-process, and in this case WebView2 is rendering trusted code written by Microsoft that isn't going to try and exploit the renderer (HTML email is very limited, doesn't support JS at all).

Processes in Windows are very expensive objects. They could probably reduce the overhead by allowing more customization of the Chrome codebase for this. Mojo abstractions service location.