My justification based on that convo was that since the SASLP/SAS2LP are very problematic and not recommended at all was to remove the test altogether rather than invest the time and energy in debugging a double check to see if the IRQ in question was using the mvsas driver (not to mention if it was another sata controller utilizing the interrupt)
Basically, I look at everything that FCP tells people to post about, and keep a tally of the answers. If the vast majority of answers is don't worry about it, then the test winds up being more trouble than its worth for all concerned.
On the other hand, for those few users where this actually does affect things, the nobody cared message is logged, and when asking for assistance on the forums it can be easily discerned via diagnostics