"New security checks in kernel heaps were added which makes "svchax" require extremely precise timing and trickery to execute, breaking it (possibly permanently) unless a fix is implemented"
Trickery, perhaps, but it's unrelated with timing.
We will be able to run svchax again if two conditions...