Honestly, I'd say the opposite is true. The more the language design changes, the more implementor time is going towards servicing the changes and not squeezing the fat out of the implementation.
That being said, the two often occur together because changes are exciting and attract effort.
I don't see how that follows at all. If the biggest issues with Ruby are performance and memory management how does changing the language spec help fix that? If anything a stable language spec should help nail down the bugs in the engine.
Python's warts have been fixed and will continue to be fixed. I cant really say the same for Ruby, especially for MRI.