I'll be honest. The person that set a deadline and forces the programmer to translate the code up to the patch day should be fire. This is the reason why the communication team members are getting blame and flame by several players from the whole player base. You clearly stated that the NA/EU internal team members are unsure about changes - what will be in the patch and what will be left out.
Here is a solution:
From what it looks like your sprint is every 4 weeks and I'm assuming you guys are using Scrum method. I hope your team are, if not the person who decided not to use this approach should be fire in all honesty. Scrum is one of the best method for implementing feature(s) because it is flexible. But back to the solution. When a sprint (with larger project it will be after multiple sprint) is over your team can wait a week or two to fully push the feature(s) to the public. Within those two weeks, all the communication team members should and know what will be on the patch. This will allow good flow of communication rather than "We don't know if that feature(s) will be in this patch or not" moment. By the way, stating something like that is very unprofessional because its clearly show the flaws in the communication among NCSoft NA/EU team members.
P.S.
When I say communication team members that include anyone that provide the player base with information, such as Community Manager, Producer, etc.