Uh, no. We're literally doing the opposite. We used to have our own caching infrastructure for "Always Online" and we're getting rid of it and using archive.org instead.
We tell archive.org about the URI, they crawl it. They handle robots.txt.
In my experience, the site owner must email archive.org support to be excluded from its crawler and archiving.
[1]: https://boingboing.net/2017/04/22/internet-archive-to-ignore...
The original Always Online infra was long unloved and probably kept on life support far too long for lack of want to deprecate an early feature.
How does what you do now contradict what you will do in the future? What legal assurances are there that you won't do hat when you leave? (See Facebook/Oculus "no Facebook account promise")
Why don't they skip this step and just keep what they have now, then? No one seems to be up in arms that they currently provide their customers offline caching...