Steven, Veeam Monitor cannot really give false alarms because it does not generate hardware alarms by itself, and rather queries those from ESX hosts. However, if there is a bug with SMASH implementation with specific server/vendor, that would result in false alarms.
Concerning "VMware Rollup Health State", this issue was reported before on this forum, but I cannot seem to find it (probably the thread got deleted by original poster). Anyway, as that poster has indicated, there is a known SMASH bug with some specific server model from specific vendor that results in this particular warning improperly reported by CIM/SMASH API; that server vendor is planning to address this with a future update. Unfortunately, all specifics are lost with the thread deleted.
Concerning bus resets, if you do not have a lot of them then I would not worry. When we had real storage problem in our lab once, the disk issues graph was going crazy with multiple resets.