Probably not for most use cases, but definitely if you have a dynamic host-based addressing scheme. In fact, my company uses a wildcard for an S3 compatible object storage service we've built in house.
A wildcard cert for example.com covers any <bucketname>.example.com our users create. Going round trip on requesting and issuing certs for each bucket would add significant delays.
Makes sense. I can't quite figure out Let's Encrypt's (what an odd construction) policy on ultimately supporting wildcard certificates, but it sounds like they're generally opposed but not completely decided. Maybe they'll end up supporting it eventually.
A wildcard cert for example.com covers any <bucketname>.example.com our users create. Going round trip on requesting and issuing certs for each bucket would add significant delays.