No, no happy medium unfortunately.
FWIW, we do have a customer who went for option 2; two geographically separate nodes in a single cluster. It mostly works, but they do complain from time to time of a split-brain when the WAN has problems. At which time we remind them that we recommended not doing what they are doing.
That said, the most recent Hazelcast plugin should recover from split brain better than before, so you may find option 2 is “good enough” for you, depending on your exact use-case. You will have to ensure that you disable the multicast cluster discovery and enable TCP/IP based cluster config, with appropriate additional configuration, as multi-cast will not work across the WAN.