Looks nice.

I agree about the markup and css in the 2.0.x default. Quite a bit of it was down to having to support roundy corners n stuff in cruddy old browsers like IE6. The decision had been made to use the curvy theme, and the decision had been made to support IE6 and IE7 (remember this was over five years ago, originally) so markup and css had to be built around that. That doesn't account for all the bloat, but does account for a bit (particularly in markup).
Funnily enough I'm doing a responsive theme for the site I run at the moment. I've rewritten around two dozen templates but it's going rather well. Works from 240px wide up to whatever. Profile is about the only area not finished. I'm not going to worry about admin.
Like you, I have no qualms about ripping out crap I don't want and throwing it away. Trashing default crud you don't want is one of the great joys of theming, IMO.

ETA: Oh and while I think of it, I actually changed my mind over my earlier posts in this thread. I am using the one theme for everything, but I'm not relying on media queries for most of the work. IMO, media queries are best for fairly small-resolution dependent tweaks.
What I've done is have the one set of templates and a custom $context['browser']['is_mobile'] in Sources. That allows me to switch large chunks of markup and php with minimal checking, to get something that works well on phone or desktop. Mobile will get one css sheet of its own (to minimise code and http requests). Desktop/tablet gets a different main stylesheet, with subsidary sheets (only tiny) to deal with the various layout options I've made for desktop.
Mobile layout is auto-loaded, without resetting the layout options in profile, so members can log in from their phones or desktop without having to change their layout settings.
Seems to work.
