Agreed that this is not an optimal solution. But if I want to know where an error is, and quickly, this method does seem fastest for most IO related errors (it stops immediately there is an error!).
Sometimes, for whatever reasons, there isn’t time or space to backup to another server (although, again agreed, this is the preferred method).
As stated, this is NOT a substitute for DBCC CHECKDB, but a quick ah-hoc method of finding the most common errors very quickly.