This would have been a viable path, when WebKit was still "a thing" and enjoyed some integration. I guess, with WebKit2, things became more complicated and resource heavy. Given the rapid development cycles and feature releases, I doubt an integrated web-view would be able to keep up, nowadays. Esp., if nothing short of 100% compatibility to current Chrome will do.
(That said, Firefox 78.15.0esr works still fine in most cases, but I doubt that this will be the case much longer, mostly because of CSS feature adoption.)
(That said, Firefox 78.15.0esr works still fine in most cases, but I doubt that this will be the case much longer, mostly because of CSS feature adoption.)