The obligations only kick in once the game gets shut down

I'm afraid that's a misconception: in most cases the obligations have to be considered during development.

in 95%+ of cases, you can't "just release the binaries", because the developers usually don't own all of their assets/code.

modern coding, and especially game dev, is highly modularized.

you usually don't build code from the ground up, if there is an existing solution for what you need. (some indie game devs still do that, but it's usually because there isn't an existing solution, or not enough budget; it's not the usual approach)

so for example, you wouldn't create your own networking solution for a multiplayer game, you'd just use an existing solution.

but because you didn't write that solution yourself, that part of the code either needs to fall under a license that allows for redistribution, or it has to be removed before you "release the binaries".

and removing such code after development is a huuuuge headache. this is something that needs to be planned for during development in most cases.

so yeah, there is some upfront cost associated with SKG, mostly in that the new regulations would need some rethinking about how to handle these code modules.

either through new or more open licenses, careful design that allows for the removal of problematic modules before release to the community, etc.

it's not a big cost, but it is there. and creating new requirements for the code, integrating that into review cycles, testing the removals, and on and on the list goes. it's mostly a management issue, but it's by no means trivial.

not that any of this is a deal breaker, but it should be kept in my mind that these new regulations are not entirely free... it's gonna cause some chaos in the industry. manageable chaos, but all chaos is somewhat expensive, when it comes to industry.