The global durable timestamp is bound to the stable timestamp and there's no reason to do that.

The User Guide documentation for the global durable timestamp is wrong; it should match the Reference Guide, and additionally should note that rollback-to-stable sets the global durable timestamp to the stable timestamp.