Yes, that's unfortunate and I think he's handled it well there. It was the same with the guy who did a windows implementation, didn't want to work with the upstream so is rife for fragmenting the protocol long-term
Given that WireGuard has been designed to be relatively simple, maybe multiple widely used implementations will make sure it stays that way.
Disclaimer: My employer sponsored a lot of the work with Jason for the windows wireguard port. (Search for "Accelerating Windows Development on https://www.wireguard.com/donations/)
[1] https://lists.zx2c4.com/pipermail/wireguard/2019-March/00403...