The problem is that the unity8 nested server BufferStream has not been assigned a frame_clock (doesn't know what monitor to sync to), so it's defaulting to unthrottled behaviour even though the swap interval is 1.
This problem should probably occur with any nested server. However it was not noticed in testing because it will only be perceptible if your nested server is also slow enough that its rendering period aliases visibly with the physical screen.
OK, I think I understand this now. Maybe.
The problem is that the unity8 nested server BufferStream has not been assigned a frame_clock (doesn't know what monitor to sync to), so it's defaulting to unthrottled behaviour even though the swap interval is 1.
This problem should probably occur with any nested server. However it was not noticed in testing because it will only be perceptible if your nested server is also slow enough that its rendering period aliases visibly with the physical screen.