Yes, it’s true that if there are going to be resizes of the GoView control, or if there are other changes which cause scrollbars to appear or disappear, it will invalidate the whole control.
If you want to optimize out the painting during this initialization process, you can call GoView.BeginUpdate() followed by GoView.EndUpdate().
Even better, call GoDocument.BeginUpdateViews() followed by GoDocument.EndUpdateViews(), which automatically calls the corresponding GoView methods on all GoViews that are displaying the given document.
As a reminder to all who might read this post -- don't perform unnecessary "optimizations"! Improper or premature optimizations are a leading cause of bugs. Only do this kind of optimization when you can prove that there is a significant improvement, and that you are correctly implementing such optimization.
That's why we tell people not to set any "SuspendsUpdates" property, even though it's available. I think calling BeginUpdate/EndUpdate is safer than setting SuspendsUpdates, but you still need to make sure the calls are always paired up (use try/finally!) and only called when you are sure it's worth it.