I take that back, it seems to have been caused by Chromium all along (more specifically either #threaded-compositing-mode or #deadline-scheduling), despite those glitches appearing outside of Chromium too. Sot it’s a Chromium bug, but I’m too lazy to debug this further (the issue goes away with those configuration flags set to default) so I’ll just mark this as invalid.