No, these 15-second delays does not cause corruption on their own. SQL Server is too smart for that.

However, those error message indicates that you disk subsystem is not to par. 15 seconds is an extremely long time for a disk access. In you original post you said We know our average read/write wait times are generally below 50 milliseconds Well, 50 ms still above what is acceptable for a spinning disk. And 1.2 seconds you mention for tempdb is outrageous.

As Kevin hinted at, getting a SAN to work properly with SQL Server can be a challenges, not the least when it comes to talking to the SAN guys. And if there are other systems using the SAN as well, predictable performance can be really difficult to achieve.