I'll do what I need to do and it's not that bad.
But, what you are saying isn't actually right. Any serious site (which mine is not, to be fair) runs development, test, staging, and production. Various tools are used to prop content and code across these environments.
Here is a post in which the author is able to simply replace his entire d-b in either direction. When the various environments are carefully managed to be as nearly as identical as possible then this is manageable. http://blog.bigsmoke.us/2008/07/12/separate-development-environment-for-wordpress
This is, of course, not the only way to do it. Another poster uses phymyadmin backup and restore to move between development and production. This is what I will have to do.
Not many people in the blogging world even care about this but in real applications, it must be done. My goal was to build and test everything on my dev server and then prop it to Hawkhost when complete. That is going to be harder than I wished it was. But, I am doing it early so the backup/restore processes, which are normally very slow, won't be that bad.
For changes in scripts, css, this is not a problem as I can ftp to file directories I have access to on Hawkhost.
I am surprised you haven't seen this among larger, commercial sites that you host. It is pretty much standard practice. But, if you are sharing an instance of MySQL across multiple customers, which seems like a truly terrible, terrible idea by the way, then this is impossible. This approach also assumes that production can be stopped for a window of time.
Note that it is just a one time problem to bootstrap from old Typepad blogs, which already contain content, to WordPress hosted on Hawkhost. Normally, little to no content would move back and forth between development and production.
So, aside from the intellectual discussion there are no worries. I'm talking a whopping 4M of data. It's 81 posts, some of which are quite long and I wanted to "automate" it. Backup and restore will work.