But on a serious note, yes, it would be nice if there was some pre-built container that just served the OSM tiles on an HTTP port. I imagine most people integrating OSM want to use their existing static-file-serving setup, which is why it doesn't already exist. (Or maybe it does, I haven't looked.)
In the end, Google Maps is free for 25,000 map loads per day and you don't have to run any servers. I'm guessing this is why it's more popular. The $5/month the OP ballparks as a price is how much Maps would cost for 760,000 map views per month. In the end, I doubt you'd do a lot better than that unless your bandwidth is free or you're serving a lot of maps. This, I guess, is why OSM isn't much more popular. The map data ends up not being the expensive part; bandwidth/hosting is.
I think the innovation in OSM is being able to use it for whatever you want. Garmin bike GPSes don't even use Garmin's own map data anymore; it's apparently cheaper for them to just use OSM data. That's because they don't have to pay the bandwidth hosting costs, they just dump the data out of the database and give people that care an update every 6 months. Each incremental map render costs them nothing, and nobody can stop them from using the data however they want. Pretty interesting that it ended up a better deal for them than using the maps they collected themselves (and probably supplemented with other vendors' data that won't let them use it on that "download once, use forever" model.)
This statement is true for a few more hours. As the headlined article informs us, Google changes its pricing plan tomorrow, 2018-07-16. Instead of 25000 free loads per day, as of tomorrow people get USD200 credit per month, on accounts that now must be backed by credit cards (or have billing enabled). Google tells us that a credit of USD200 per month is equivalent to 28000 free loads (of a dynamic map) per month (not per day).
* https://cloud.google.com/maps-platform/pricing/sheet/
* https://cloud.google.com/maps-platform/pricing/
Hence the timing of the OpenStreetMap article, of course.
Plus volunteers to answer any and all support requests? And the tile rendering needs to be fast? $5/month isn't enough hardware to a world-wide tile server and it sounds like users aren't willing to pay for setup costs.
> just want to "throw in a map", I don't want to spend a day+ doing it.
There's plenty of SaaS offering OSM tile hosting. If those are too expensive (quite more than $5/month, some have pay-as-you-go pricing) it's an indication running those servers is more complex than it seems.
> Where the whole process shouldn't take more than 10 minutes
That said, check out https://openmaptiles.org/docs/ installation. (They will charge up to 1000 USD for commercial use, free for personal project).