Windows naturally tries to deference NTFS junction points, much like Linux automatically dereferences mount points and symlinks. You can't get around this directly in the Windows OS, as Windows needs junction points to operate correctly, except possibly when using an alternate shell in Safe Mode, although this would probably have some interesting side effects while logged in. The only way to "disable" a NTFS junction is to delete it entirely, not something you could do in read-only mode.
What you can do, however, is not use Windows directly. For example, boot your system in Linux, possibly using a cheap USB stick and a Linux-on-a-stick, and you can mount the image directly into Linux, and perform all the find operations you want without worrying about it wandering into your hard drive, since your drive won't be mounted, and Linux has no notion of drive letters anyways. Your mileage may vary here, as NTFS support, while quite excellent, is not quite as good as Windows' own NTFS support. Personally, I would just as soon whip out a copy of Ubuntu USB version, boot it, mount the image, and go exploring.
Another excellent alternative would be to simply mount the drive in a VM running Windows. You probably qualify for Windows XP Mode if you're using almost any modern version of Windows. Install, mount the drive, and examine to your heart's content. Since you're in a VM, any damage done to the drive will only harm the VM, and not your computer. You can reinstall it as many times as you need, and as long as you've backed up that hard drive image, you can "reformat" back to that image as often as you desire. At that point, you could recklessly experiment with deleting those junction points, assigning a new letter to your boot drive, etc.