/stopcasting in 2.3

I read another thread with a lot of discussion about cast latency and /stopcasting with regards to 2.3.

Slouken said:

Q u o t e:
"The current thought is also that we won't be sending casts to the server during the global cooldown, both to reduce bandwidth (and flood disconnections) and to lessen the incentive to spam cast."

I want to clarify which casts are being referred to. If I have a macro that executes

/stopcasting
/cast Nature's Swiftness
/stopcasting
/cast Healing Wave

then I am absolutely depending on the fact that these actions are sent to the server even though my client thinks I'm inside the GCD. The logs prove that this does in fact work:

10/23 20:34:22.156 You fail to cast Nature's Swiftness: Not yet recovered.
10/23 20:34:22.157 You fail to cast Healing Wave: Not yet recovered.
...
10/23 20:34:22.159 You fail to cast Nature's Swiftness: Not yet recovered.
...
10/23 20:34:22.237 Your Healing Wave heals Heketoro for 4121.

(the time stamps prove that NS + HW did in fact go off)

Will this continue to work in 2.3? More people will die if I have to wait for a client-->server round trip before the NS and HW are sent to the server, and that would be a regression from 2.2, and it would penalize higher latency connections more than lower latency ones.

Thanks,
-Jindi