the only way to know for sure whether RTMFP will work is to try.
you might be behind a NAT or firewall that could allow a connection to Cirrus but that would block most P2P connections. or you might be behind a firewall that blocks UDP altogether, so you couldn't connect to Cirrus at all.
"connecting to Cirrus" pretty much means "UDP to ports 1935 and 10000-10100 works". any other UDP connectivity test on some other port would be be similar except it wouldn't tell you about the ports you really care about, and testing it would probably take about the same amount of time to be sure.
you can always set a timer to give up earlier than the RTMFP connection timeout time. for example, if you don't get an RTMFP connection in 5ish seconds, you could bring up an RTMP connection to AMS, while continuing to try the RTMFP connection. if the RTMFP connection eventually succeeds, you can preferentially use it (or switch to it), but if it doesn't come up, at least you'll have built your fall-back channel sooner rather than later.
if you're having RTMFP connectivity problems, take a look at the RTMFP Connectivity Checker diagnostic tools:
http://cc.rtmfp.net/ (IPv4)
http://www.rtmfp.net/cc6/ (IPv6)
