It's nothing to do with DBCC - it's the try/catch eating the errors being printed. No idea how to use that correctly - it has some weird behavior.

Nothing changes the behavior of DBCC, but you're changing the way the DBCC output is consumed.

All I said was after running DBCC, the value of @@error will be non-zero if errors were found.