It is a common misconception. Browser != rendering engine. It takes tremendous effort to build an iOS browser even when you have WebKit as given as you need to build every single browser feature from scratch. "Open in new tab"? "Favorites"? "Download file"? "Switch tabs"? "Find on page"? All of them need to be built. I know because we are building one.
Chrome on iOS can do pretty much everything it needs to do - settings, telemetry, sync, any kind of custom browser chrome and features and is a _very_ different browser than Safari in many important aspects. For a few that particularly matter to user - consistency of web page rendering, performance and battery life - the user is actually better off as they get a rendering engine built by the phone manufacturer.