Verifying backups is another story. Well, it's kinda connected, but still another one.
It's possible to do robust verification of SAN backups as well as SQL backups.
So, I would not put the blame for not having it on the technology itself.
It's just rarely anybody does it, because of extreme costs of the procedure.
If they brag about the ability of making backups every 1/2 hour, then it's likely they would not be able to restore that backup on another server and verify its integrity within the next 1/2 hour. Most likely, not even within an hour or two.
Which means - the verification will fall behind and will be inevitably skipped/abandoned.
But even if the verification is established and done properly - what extra cost is incurred?
How many times more data stored in SAN backup comparing to SQL DB backups?
How much more space you need to allocate the snapshots?
But what rate it increases disk IO? 3,4,5 times?
If you use SSD, it directly translates to the next question - but what rate it shortens the life span of the drives?
How much more computing power is required for verifying the integrity of SAN backups (and the integrity of every DB file inside of that backup) in timely manner comparing to verifying SQL backups?
You mentioned, you're working for a small company - those extra expenses might not be that easy to ignore for them. And I'm sure you'd better see those funds directed towards your wages rather than to hardware maintenance.