Hi, everyone,
I just want to update everyone on this situation. My issue (see above in this thread) has been resolved completely and I no longer even need the "workaround" that I was using before (which was to use DisplayPort daisy-chaining).
- MS replaced my Surface Dock 2. That may have helped (I say that without certainty because the sequence of troubleshooting I took obscures exactly what issue it may have fixed, if any). Thanks, MS!
2. I rerouted my cheap USB-C to DisplayPort cables through the cable hollows of my dual VESA arms, thus isolating the video cables from power cable and everything else.
This 100% fixed all of my issues. I have no sleep/wake issues, no second-display-failing issues, no nothing. Zero issues. Not so much as a single flicker in one display. The displays work exactly as you'd expect them to. This has been the case for more than a week now.
So I think this may explain why using certain adapters or more expensive cables might help: perhaps that results in better shielding of the display signal throughout the path from the dock to the display.
It may also explain why daisy-chaining helped me too. It may have been just a coincidence: The signal path when daisy chaining just happened to run into less interference from, say, monitor power cables.
I still suspect that Windows is at least partly to blame here, as it could have handled the information it got from the displays at different times differently and thus provided for a seamless experience. But that's just speculation on my (non-engineer!) part. Also, I don't know how recent Windows updates may have addressed this (though I saw nothing in the update documentation that would suggest that).
Hope this helps someone!
Andrew