I don't think so. MC-4 is a desync between client and server, this bug is caused by floating point precision errors. These are completely different issues.
Kubuntu Linux 18.04.1, Minecraft is on HDD (Seagate ST1000DM010-2EP102, 1TB, 7200RPM, 64MB cache)
The same bug also happens when returning to the overworld via end portal (which attempts to place you at your spawnpoint), but since this doesn't involve death you can just reload the world without getting softlocked into the death screen. So it seems any attempt to respawn a player will cause this bug.
Interestingly, when triggering the bug this way you can still run around but the internal server won't register anything you do (breaking/placing blocks, going through portals etc.). So for instance, if you break a block, it'll become a "ghost block" as the server still thinks it's there, and when you quit and reload the block magically comes back.
I would gladly do so, but I'm unaware of any way for me to transfer ownership; from what I understand, a moderator has to do it.