Was that the actual problem with Edge tho? My problem with Edge was always the UI and lack of customization. Edge was already very standards compliant and didn't require an abundance of special testing like IE
Take one of the top posts on HN today, left is a Chromium based browser and right is Edge: https://i.imgur.com/C6WRaAD.png
The other browsers are very standards compliant, doesn't matter - still broke.
because it wasn't made to be standards compliant. It's just an art project someone threw together in 2 hours, not an actual website.
Also I recommend checking out the post/page if you think it was just a 2 hour pump and dump css show off. It's multiple pieces made by handwritten LESS on the order of 4,000 lines over hundreds of commits per drawing.
When I tried to use Edge, I found the same as you, but I also had a lot of sites (particularly "app"-like experiences) break in unusual ways or outright refuse to load. But I am also looking at developer-targeted stuff more than a normal user might so YMMV.
Developers didn't "care" about Edge, so sites break (or are incompatible), and users weren't buying in because the upsides of Edge didn't out-weight the downsides (breakages).
Now nobody has to "care" about Edge-Chrome because if it supports Chrome, it supports Edge-Chrome, and therefore users can use it for a lower perceived cost via the lack of breakages. Then it is just up to Microsoft to add just enough unique features/value-adds on top of Chrome to outweigh the little to no downsides.
Plus Microsoft likely saves money over developing/maintaining their own HTML rendering engine. So the amount of gain they need is much smaller to make it successful.