Lets Encrypt has a limit of 20 domains per week for you.
So you end up with at most a few hundred users.
https://letsencrypt.org/docs/rate-limits/
If that's not enough for your use case, you're probably big enough that a wildcard cert is a negligible expense.
We're talking about edge-cases within edge-cases at this point: a service that (1) offers HTTPS subdomains (2) hasn't been able to get a rate-limit increase from Let's Encrypt (3) is unwilling to buy a wildcard cert (4) either is growing by hundreds of subdomains a day, or has a significant amount of clients who can't wait a few hours for a cert but won't buy their own. That's so oddly specific, I'm not surprised people aren't going out of their way to cater to it.
If I want to build my own little Github sites, I'd already run into the problem.
And, in fact, I've run into the limits several times before, and had to use startssl certs for far longer than planned because of that.
Let's Encrypt and certbot. It's all but trivial to SSL your site and keep it up to date if you control the system.
Here's how I SSLed my blogs. This was interactive, but fully scripting it would be easy: https://rocknerd.co.uk/2016/12/04/rocknerd-is-now-fully-ssl-... Took me literally minutes to set up, it took more time to track down the http:// images to fix the mixed-content warning.