Also you could delete the browser (iexplore.exe) but not the engine as the OS relied on certain UI elements that used this engine. Ofcource if you went ahead and deleted the DLLs anyway, you could make the OS work without the added HTML UI layer (as the judge in the MS antitrust case demonstrated). One could argue that this wasn't the "full" Windows experience but hey.. all that is water under the bridge now. The case is resolved and MS got slapped with a hefty fine.
And then I believe the help component also relied on the rendering engine. Although the hcp:// vulnerabilities were in the protocol handler (helpctr.exe) and the ms-help:// vulnerabilities were also in the protocol handler which allowed the attacker to bypass ASLR/DEP.
It's funny, when the Windows source code was leaked (opened?) in 2004[1], folks soon discovered a vulnerability in the BMP renderer[2].
[1] http://slashdot.org/story/04/02/12/2114228/windows-2000-wind...
But OTOH these bugs become useful in other ways. I believe there was an ios jailbreak method where you simply visit a website on your iphone (jailbreak.me? .com?) and your device is rooted/jailbroken due to a bug in Safari's PDF renderer.