Looks like this issue has finally been resolved, by way of the new NVIDIA 302 drivers supporting XRandr!
Looks like this issue has finally been resolved, by way of the new NVIDIA 302 drivers supporting XRandr!