Nexon: Can and Can't.

Only valid if you actually know who did what, and you in particular have no idea what portions of our work get done by local development and which get farmed off to Korea. The local devs maintain the hardware, databases, and do routine crap. Anything else comes from the portion of the KMS team that is designated to support our locale. GMS may ask them for things, and submit wishlists, but that doesn't mean they actually do the work.

The exact interminglings of their office are hidden behind obscurity (so that, unless I'm mistaken, none of us know exactly who does what), it's true, but that's not the core issue here.
The issue is that, whatever the system is, it doesn't work.

If every bit of engine altering code has to be, at minimum, run by the Korean branch or, at maximum, constructed directly by them, and that system is what has resulted in the current clusterpineapple, then that system needs to be changed, not excused.

If Nexon America has to ask permission to wipe itself, then maybe there need to be people with that ability to grant them permission in-house so that massive issues can be dealt with more quickly and effectively (or even avoided entirely).

Much like Nexon America has certain obligations to its consumers, Nexon Korea should have certain obligations to its subsidiaries.