Hi, as you have additional infrastructure between the units there is a higher risk of split-brain active/active (same traffic-group going active on both units) and therefore you should consider the connectivity between sites, switch fabric, perimeter firewalls, routing, underlying mpls/optical connections/diversity to understand the availability/SLA of the network connection so that it matches your F5 availability design. Using TMM and mgt will give you diversity locally but if there is a single point of failure somewhere and TMM and mgt follow the same path it'll not be good.
It may be unlikely to have a routed only network between F5s in different DCs if they will present the same applications (VS IPs) at each DC
cheers