Have to disagree here. Anything remotely complex with JS usually doesn't work as-expected after archived on Internet Archive. Keep in mind we're not talking about a LAMP-driven WordPress blog with some jQuery sprinkled in - we're talking about an actual piece of software running in the browser ie: device driver.

In good faith I would not expect something which uses experimental browser APIs to maintain functionality when archived by Internet Archive's automated crawling solutions. Same applies to offline saving.

Good point regarding the offline capabilities, I'm not sure how well the Internet Archive will handle Wasm, but for the rest - WebUSB was already stabilized and isn't considered experimental (although I admit that didn't stop some other non-cross-browser APIs from being removed in the past).

Archive is a little flaky on this front, but the other issue i see is when the company decides Archive is illegally hosting and files a DMCA or other lawsuit

Companies that want to do so, already embed "ring home" mechanisms in their apps that periodically connect to the Internet and check that you still hold a valid license or refuse to continue working.

It seems this depends a lot more on the company policy rather than specific technology used for the implementation.