I started w/ Slackware and moved to Red Hat and then Fedora but eventually RH and Fedora became "the Linux that couldn't" when I was installing on either an old or new machine. On the same machine Ubuntu would install just fine.
I run a Windows desktop now and mostly use Ubuntu Linux in AWS, sometimes inside a VM on my local machine. I used to run the RH-derived AWS Linux, but eventually I learned how to do things easily in Ubuntu, such as installing and maintaning an Oracle JVM, that are hard in Red Hat. Definitely an enthusiast could find a solution with RHEL, but having a server OS that "just works" is what you need if you are the guy who splits his time between devops and bizdev.
That means that for N cloud hosts Red Hat would have to potentially build N different patches for any update or security fix.
Now you can't certify software to run on "RHEL 7" anymore, it has to be "RHEL 7, assuming it has XYZ, which some cloud hosts don't".
It can be done, but it's a huge hassle, it's much easier to just ship the same distro to everyone. Space is cheap.
Why would they have to do that? AFAIK, patches apply to packages, not the entire distro. If $package_x isn't installed, it doesn't get the patch. If it is installed, it does get the patch.
And for me, the concern isn't space, as much as running processes, and littered un-needed files.
I think this whole line of argument is just some misplaced nostalgia for distro micro-optimization. It's not the mid-90s anymore. Space and CPU is cheap, you're not going to gain anything significant by trimming down your distro.
If those things were actually important you wouldn't be using Azure in the first place.
[1] https://aws.amazon.com/marketplace/review/product-reviews/re...