That's not computer science, that's software engineering. If that's what you're interested in, you could look at RIT. That said, I'm guessing you're in high school, which means you may well not really know what you want. Personally, I wouldn't recommend doing a software engineering degree. If you get a solid CS education, the software stuff is relatively easy to pick up.
If you can get in, I highly recommend Stanford. Your chances of doing research as an undergrad aren't great, but you'll learn a lot, meet smart people, and classes like CS210 will give you a little of the practical software experience you mentioned. Plus, it's an awesome undergrad experience, one that I'm sad I missed out on.
If you want to do research as an undergrad, I know from experience that this is possible at Georgetown. The department there is tiny, but has several good professors, and many of my friends there did research as undergrads. There are definition downsides to doing CS there (department has less resources, you're unlikely to meet any potential cofounders, etc.) but overall I think I got a good education there (enough to prepare me well for a MS at Stanford, anyway).
I would expect that as ramchip notes informal arrangements can be done most anywhere, although getting paid in any way other than experience may not be.
One maybe not so minor note: according to one school that is ABET accredited, only 210 in the US have ABET accredited CS programs. E.g. my home town 4 year public college doesn't have one, I'd have to go to a larger regional one 70 miles away.
If he wants something very "applied", there's also computer engineering. I've been doing research since my first year as an undergrad (mainly through Canadian research grants, which offer paid summer internships). We do mainly C++, Java, VHDL, Verilog, assembly, but there's fairly little actual language education - they teach the semantics, we learn the syntax by reading and trying stuff.
On the more CS side of things, we did state machines, graph theory, recursion, formal proofs, and a good dose of math: solving differential equations analitically and numerically, calculus applied to force fields, Laplace, Fourier, complex analysis etc. Of course there's also electronic circuits, networking, computer architecture, (object-oriented) architecture... It's possible to study more web-related things such as databases, but I'm in embedded systems so we don't really touch this.
It's as applied as you can get: I have co-authored several papers and I'm only in my third year. But if you want to do research, you'll have to work for it a little. Go speak to teachers, do projects on your own, etc. AFAIK it's possible pretty much anywhere, but you won't necessarily get paid for it or get to choose your topic.
By "diverse" I mean going beyond software engineering and touching on graphics, AI, simulation, AR/VR, hardware architecture, and so on. My main worry is ending up in cookie cutter classes for four years. Then again, my idea of what college is truly like may be skewed due to the romantic idea of higher education that is sold to us in high school.
Thanks for the suggestions!
More generally, I think the anti-education sentiment you mentioned is unfounded. I'm colored by my experiences, of course, but I don't think I'd be half the engineer I am today without the education I've had, and I'm not a stupid guy.
Also my favorite Quake server (kitty1.stanford.edu) was run from a Quake CS Lab :)