Sorry for the late reply.  Yes, I think this change should be merged.  I'm pretty sure that since we no longer have a custom nodeToParentTransform, but instead use the base CCNode one that all the scale and scew properties will be correctly honored.
Indeed if it had been implemented like this to begin with than I don't think the issue being refereed to would have occurred at all.

I will verify by running the test case in the forrum referenced forum topic and get back to you to confirm.