Ideally just the Trident rendering engine (in MSHTML.dll) could be ported to other platforms for web developer use, but I don't know how reliant on other Windows features it is. I also don't think it's much of a priority (or at all feasible) for the IE team to re-architect their entire product, but I would love for them to prove me wrong.
No idea why not, but it's a different group than MS's other Open Sourcing efforts; The Dev tools people are happy to show their ASP.net mvc work[1], among other things[2], but IE falls under their Windows group, so it's a different set of people making the decisions.
[1] http://aspnetwebstack.codeplex.com/SourceControl/latest
[2] https://roslyn.codeplex.com/SourceControl/latest (hell yeah)
I can see them doing it with IE mobile though as they aren't the most popular player in the mobile market and they need to get people hooked.
I wouldn't bet on Microsoft and Apple ever suing each other again.
I honestly do my best to test across all the modern browsers when I develop, but having to spin up a random VM running whatever version of windows they require for whatever the edge version of IE is starts to get old after a while.
If the Chrome and Firefox teams can maintain multiple architectures and release them in lock-step, it's certainly possible for Microsoft to start on the road to this process, even if it takes them a couple of years.
And would open-sourcing the browser really kill them?