There are some fundamental constraints there for both cases you mentioned, but more so Netflix. Their business model and physical infrastructure are structured around a small, popular, catalog. This enables dense storage utilization at the edge, optimizations like pushing content during troughs, etc. Because of that they're edge is generally optimized for a small number of bytes stored and a very large number of bytes served to clients.
Storing a large number of "cold" or "long tail" bytes is a different physical problem when it comes to storage and IO. And that's also the exact problem you have when hosting lots of third party content (or apps, or lambdas, or anything else). There you're also optimizing for bytes stored:served, but have to place it on cheaper media and with less duplication to make the physical space/power/dollar constraints work.
They certainly could change their business model and infra. But then they end up looking a lot more like a commercial CDN with hierarchal stores, more centralized POPs at IXPs, etc.
Disclaimer: Principal at AWS. Used to work on Amazon CloudFront and a bit of time in AWS Elemental, served a lot of video & streaming bits. Everything above is public domain knowledge.