Bharat -
Nope, no need to stop the ADC during cross-site moves. The problem during within-the-site moves is that if the object is changed somewhere else in the 5.5 directory before the ADC can replicate in the "new server" info (HomeMDB/HomeMTA) from the AD, the 5.5 change is newer and overwrites the values in the AD. All of a sudden, all of the mail is on the target server, but the new inbound mail is going back to the original server. KB.299473 talks about this in more detail.
In cross-site moves, since the source object becomes a "stub" object, it doesn't really matter much for mail delivery. X500:ADCDoNotReplicate is set on it, and the ADC will ignore it if it is updated with incorrect values. The (new) target object is created in the target site using the (correctly updated) AD info.
So, it DOES matter that the ADC is not replicating during mixed-mode mailbox moves in the traditional sense. But for mixed-mode, cross-site moves with the Exchange 2003 SP1 feature, there is no need to ensure the ADC is not replicating during the moves.
Hope it helps!
Evan