The approach he described is consistent with non-malicious failure to turn a new API into something robust, reliable, external, and well documented. If you’ve got a hot new way to move bytes the long term stability of the API is a real concern. You break things if you change it.

No. "Deliberately disadvantaging" is doing something like adding code to slow down disk write operations used by a direct competitor.

Listen, I'm not gonna play this game. I said my piece, you said yours, we're done.