Dual master is an undesired side-effect of a malfunctioning of a design. It must be avoided at all times. It's also the reason why we don't interconnect the two MX's directly anymore in an HA setup.
See also the description in the link you shared:
Dual Master: Dual Master describes a scenario in which both the Primary and the Spare are in the Active state. This occurs when both MXs are online and communicating with the cloud, but the Secondary is not receiving heartbeat packets (see VRRP heartbeats in the next section) from the Primary. This can cause several issues with Dynamic DNS, VPN, and traffic processing in general and should be avoided at all costs. The Physical Architectures section of this document describes how to deploy an MX Warm Spare pair in order to minimize the chances of a Dual Master scenario occurring.