Yes, the expectation is that if a verify runs to completion (no deletes or edits detected) then parity should match the data. This initial check is really just to avoid having an expensive, time-consuming verify fail halfway through because some file got deleted or moved.
An added file doesn't cause the verify to abort, because files added since the last update won't cause a verification error (verify checks the parity data against the files that were present at the time of the last update, so files added since then aren't in the parity and won't be checked.)
When I said "any changes" in my post above I really should have said any deletes, edits, or moves.