A custom tld is only custom until it's not (see .dev, .corp), and using them for intranet purposes is widely regarded as bad practice.
If you're already serving regular content over HTTPS internally, then I don't see the big issue in serving video and images the same way, but I'm not familiar with your particular use case so you may of course have a point here that I'm ignorant of.
