Most of the "the replay game differs from the original game"-bug reports i got contained replays that were recorded while using DjinnKahn's WarLatency program at the same time.
This is not a bug in War2BNE InSight, but rather a conflict between War2BNE InSight and WarLatency.
Affected replays abort with the error message mentioned above and Warcraft shows a "Player X set network for Y latency" message, just before the replay aborts.
To view such replays, simply

• use WarLatency, if the player who recorded the replay used it.
• do NOT use WarLatency, if the player who recorded the replay has NOT used it. (You might have to restart Warcraft II, if you have used WarLatency before, since WarLatency has no Deactivate button)

Sometimes this can be a bit tricky. I have seen a replay, in which a player sets the latency to extra high and back to low (which lets WarLatency take effect, if it's activated), then he realized, WarLatency was not running, so he activates it and again sets latency to extra high and back to low.
To view that replay you'd have to start without WarLatency and activate it after the first to-extra-high-and-back-to-low latency change.