I think the internal snapshot for dbcc is the same process as a "database snapshot" using a sparse file in NTFS, but you don't have control over the placement of where it is.

From the OP, I'm not sure what the question means. When you run dbcc, you don't get to choose to use a snapshot or not. It uses a snapshot internally, but it also hits the existing database. A "database snapshot" you have created doesn't really change the way dbcc works.