Couldn't the unresponsive kubectl issue be resolved by isolating cpus and controlling yourself where processes go?
If they saw the issue, then either they have not configured their nodes right, missconfigured them or perhaps run something very old?
I'm quite curious to see a proper test bench