On putty: I'm surprised to hear all the bad vibes for putty - what's wrong with its terminal emulation? I adore putty - you can configure it so that it toggles full-screen with alt+enter and can load sessions with windows+r, 'putty -load {session name}'. It's easy to configure different colours for different profiles so it's easy to always have my production consoles in red. I haven't found such a straightforward way of getting that going in a linux desktop setting (other than using putty for linux which is unrefined). The default font isn't all that nice but I think I use terminal size 10 and that looks nice. Putty supports all the stuff you criticise - 'text selection, copy-paste, window resizing, fonts' - what's the downside? I tend to use it in gnu-screen and don't have problems with this.

On cmd: Funnily enough that cmd environment has become less powerful over the evolution of Windows. For instance, it used to be possible in win2k era to bundle a complete application as a batch file by having code stored as text and written out when it ran - through a couple of mechanisms using minor features. Those features which were subsequently removed, presumably to stop just this sort of hack. The latest versions of Windows don't have telnet as standard - I'm at a complete loss to know how I'm meant to do connectivity testing with clients who don't have it and don't have permission to install it - the telnet mechanism in Windows was bad enough as it was but now they've made things worse. I've found Windows scripting host to be very poor for doing networking. It's also very crippled.

(When I'm in OSX I use iTerm because it's the only way I've found to get a nice full-screen console under the current release of OSX)