Yes they could, because the issue seems to be the server sending too many chunk packets in a short period of time, the client could be fixed to handle that amount or the server could send chunks a little slower, in my case i reduce the intensity of chunks sent to the client and nobody is having the issue anymore. And since even 1.8 players are having the issue when only the server is running on 1.11 means the issue should have started on the server-side. On 1.8 chunks used to be sent in bulk, now it is sent individually, the client may not be able to handle the high intensity of chunk packets and forget to render some of them.
I think this ticket is looking at this issue the wrong way, I have been experiencing this issue since I updated my server from 1.8 to 1.9, Im running 1.11.2 now and yet having this issue, it wont affect everyone, some will have this issue more often than others, but the twist is that I allow players from 1.8 to 1.11 to play and even 1.8 players started having this issue after the update, which means that this is more related on how the server (or client-side server) send the chunks to the client than rendering itself, relog wont solve the issue, but if you join in a random world and teleport back to where the glitch was happening will solve the issue (like sending fake dimension packets to flush the chunk cache), this issue also wont happen on nether or the end. I made a few test changes on the chunk sending code and I realised that if I send chunks slower, like one per tick, the world will take forever to load of course but no render issues will apear. This issue should be investigated on how the server is sending chunks and not how the client is rendering them.
Try the old launcher for now it will work just fine, me and a lot of other people are having the same issue but automatic replies is all we got so far.. my launcher log:
[media]no game logs are generated as the game dont even start..