So this is really more of an image thing -- site responsiveness, accessibility, and so forth. Similar to how a shopkeeper might have paid 2500 each year to have a sign custom-painted out front.
In that case, makes sense. I'm not an extreme cheapo -- I'm probably paying 1800 a year for my various hosting solutions, but that's spread across HostGator, a MT hosting company, and AWS. I'm moving to AWS -- exactly in the opposite direction that you are heading -- because I like buying cycles. I can set up databases, write code, and have more power to write hybrid sites. I'm beginning to look at producing content on the web, blogs, apps, static sites, or mixed-mode stuff, as more of an art form and less of a pre-canned WP experience. So I need a box, not a service.
But I look at this as simple content. I'm serving bits to folks who come and consume them. I don't generate consulting leads though my sites, I provide data people want for free, so as long as most of the people get most of the data, everything is copasetic on my end. It sounds like we have completely different purposes.
Just as a off-the-wall suggestion to other readers, you know you could write a script to consume your blog entries and move them to a CDN as static pages. You'd get a hell of a boost in performance, and I don't think you'd really have to change much. (Probably much tougher than I make it out to be. Haven't really thought it through. I use URL rewriting on some of my newer sites, so it all looks like static content anyway.)