Its not “forced obsolescence”. Its about there being limited time and resources involved in any project. And stuff like this is very specifically about making sure the game will still be viable for the people who still want to play it after the project/company is over.
The Internet so any metaphor will immediately lead to anger but: It is good practice to document processes and design decisions so that someone who comes after you can understand them. And yes, there is an argument for “job security” if you are the only person who understands how the backup server works. But it is not “job security” to slack a bit on properly documenting and filing that information because you have a million and one other things to work on.
And a lot of the “We need LAN/offline mode in case you go out of business” can feel a lot like “So… we need you to make sure that this will work if we fire you tomorrow”. Yes, a good developer will do that (because it really does reduce support burden down the line) but that is not going to be your priority when you have other deliverables or stuff you actually enjoy working on.