Assistance Requested - iRule causes virtual to hang upon LTM reboot

Thanks very much for your response - that'd be a great solution, however, we'd like to implement this iRule across a bunch of virtuals, so would like to avoid having to specify a check against a particular pool, if possible. Would the above suggestion (adding "persist none" to the iRule) remove persistence to the pool specified in the virtual, do you think?

As an aside - we haven't had to use the "Action on Service Down" option on our pools yet, as it seems the load balancer recognizes down pool members fairly quickly and routes traffic to the remaining active members. Is there a benefit to setting this option to "Reselect" rather than just leaving it at its default ("None")?

Thanks again for your help!