"Fixing" is not the correct term in there, that's why I didn't just say fix without quotation marks. Making a code piece more accessible is not fixing it but making it.. well.. more accessible.
And that can take time - however, designing that in the beginning by thinking about the modders would take more time. Especially if your design can change/gets updated/revised etc. before the deadline. And this happens quite often in the game industry.
Native and SandBox modules are required to play the native game, yes. This, in theory, same with Warband as well. Not sure what do you want by pointing this out?
I don't think that argument makes any sense ( code-wise). Patching is more compatibility friendly than basic overriding.
Anyway, this ( internal consts etc ) was how they were doing things for awhile already - so for some parts perhaps someone naively thought applying this would resolve their conflict issues with mods or in-between mods without knowing anything about patching.
But yes, let's see if TW clarify this matter or not. Or better, if they decide to take action before EA ends.
Well, this is related to their internal management and not something I can say about it.
As I said, I would support having more transparent layers and more accessible code too. But letter is kinda stating that they are being hostile to the modders intentionally and creating bumps to their roads just because they don't like to support modders right now. And that statement/behaviour is not fair.
And? It's still easy.