I could use esxcfg-mpath to get the state or grep vmkernel.log run from cron but would prefer something built in, or at least have the option to shut a VM down. This is serious for us, and we have a system due to be shipped to a customer in 2 weeks and I need to find a way to do this.
A host in APD runs on best effort basis, you cannot expect vmkernel.log and esxcfg-mpath to actually contain useful information or even log that event correctly. 5.1 resolves that issue to a certain degree due to hostd not being killed completely by an APD.
Just imagine the following scenario:
Your storage latency grows to an extremely high amount without a failover to a different path resolving the issue for whatever reason. Per definition you might not be in a clean APD but the behaviour you will be experiencing is the same. How do you intend to deal with that scenario (and yes it is valid, I see it several times per months).