Howard Miller

Unless.... there's a bug in the earlier version (LTS or otherwise) that's a "show stopper" for you. That would be unlucky but it happens.

I would add to the above by also saying that you should not put yourself in a position where upgrading is a big deal. You should have a sensible strategy to keep up to date.

Are they running software that is blocking this javascript code?

That's not my understanding. Correct me if I'm wrong.

If you have (for example) a virtual host for https://moodle.mysite.org with a document root of /var/www/html containing a pre-5.1 Moodle site. The simplest thing to do is to upgrade the Moodle code and change the document root to /var/www/html/public. This will be the case for all the people running 'enterprise' Moodle, in containers, and lots of other situations.

Yes - for 'shared hosting' it's a different ball game.

Possibly - if you get it working once, then kicking off loads more instances ceases to be a big deal.

The docs say "use a symlink" or "use an alias in your webserver" (I paraphrase). All perfectly good advice if you a) know what it means and b) have the required level of access.