I disagree. If someone can make a 2048x2048 video with 24 frames of images, this would be magnitudes faster than waiting N * 5 seconds (120 seconds in this case) with the image loader.
Is there a reason it can not be, say, X amount of requests per Y amount of time, like many rate limits do? 5 seconds per request is a lot. If it was 4 requests in 20 seconds, that would be a lot better. Though even then, I really fail to see why it couldn’t be something like 20-40 requests per 10 seconds maybe.
Modern web is designed around these sorts of bandwidth. Many websites themselves will often grab 20-100+ images within a few hundred milliseconds. Granted, browsers have a caching feature, but still. If a web server/CDN can be overwhelmed with a few dozen requests per client in a busy VRC world, then there is something wrong with that web server/CDN.
Many CDNs, DNS, or other web solutions even offer their own caching. Heck, anyone can use Cloudflare for free and it will cache all of their requests so the web server itself is not abused. This is what I do with a few of my home-hosted servers. Cloudflare even blocks DDOS attacks! Ignore the 8% cache here, as I have some services that are not behind Cloudflare Proxy. If it was a service made specifically for VRC with images and text, there is a great chance it would be 95%+.

I am obviously grateful that we do have image and string loading in the first place. But this aggressive rate limit is going to significantly limit the capabilities of creators, and they will have to engineer solutions around the rate limit. Even think about LS Media, which has thousands of images for posters. Right now, the world is 200 MB and most of the thumbnails are incredibly poor quality. Are you suggesting that a world like LS Media should have to create their own atlasing solution in code based on requests, rather than hosting a generic CDN that they can probably run out of their home behind Cloudflare?
You are preventing a problem that does not exist yet.
Even a rate limit of 1 request per 100 ms would be plenty to stop DDOS attacks or other abuse. And even then, what is stopping VRC from having a dynamic rate limit and auto-block/ban feature for worlds that are sending too many requests? This can be something that is programmed, no?
I would hope at least a better rate limit can be achieved for worlds that may need many custom images to be loaded, or data from different sources to be loaded with the string loader. If I want to load a few images and a few strings, does this mean that I have to supply loading screens and have the user wait 30-60 seconds for the world to fully load?
Here is a canny asking to improve the rate limit.