The reason I ended up using both is because there were not any useful code examples I could find for using BI 4.0 .NET SDK the way I am doing above. What I could find all required CR for VS components.
I don't believe the issue has anything to do with using both because the print, export, and refresh functionality is all built into CR for VS. If there were an issue it would make sense to have it pop up when loading the document into the crystalreportviewer; having it occur specifically when using the functionality that CR for VS provides (print, export, and refresh) which all work fine on their own doesn't make sense.