I think the underlying issue is that Google is under a lot of pressure from the EU and other governing bodies to police its YouTube content, Google being Google

I think the underlying issue is that Google is under a lot of pressure from the EU and other governing bodies to police its YouTube content, Google being Google is trying to do this with algorithms, unfortunately when the algorithm gets something wrong there is seldom much recourse beyond knowing someone on the inside or being able to raise a big enough stink on Twitter. But this is nothing new, so I think you have to go into things planning for the day Google demonetizes your videos or suspends your account for no reason. Make sure you have backups in GCP, S3, or some other non-Google facility that your kid won’t unplug while playing. Learn how to serve video yourself and have that as a backup - when promoting your video link to a resource you control so you can direct people to backup sources when needed. Thanks to Apple there are only two, more or less interchangeable, standards for playing video on modern browsers, the only difference is that one standard (HLS) is controlled by Apple and the only option on iOS, and the other standard (DASH) is controlled by Google and works on everything except iOS. Most CDNs have support for HLS which means they dynamically recode video, help to generate manifests that direct users to lowest latency locations, and help to enforce entitlements (though as far as I can tell without proprietary DRM extensions all that is good for is largely keeping honest people honest which you may not care about when making video blogs or other public consumption content)