Do you include image information in the xml you save at the end of the simulation? If not, then I would expect this behavior. If a rigid body gets split across the box boundary, and there are no image tags in the xml file, hoomd thinks the rigid body is a box width wide when it reads in the xml file.
This behavior is not possible in hoomd v2.0. In the rewritten composite body framework, users specify composite bodies in a local reference frame, and the rigid body is initialized from the position/orientation of a central particle.
Regarding visualization tools, VMD cannot draw polygon or polyhedral shaped particles. We have a number of internal tools in glotzer group that do. Some are python based and allow users to write custom workflows - i.e. coloring individual particles with different colors in a custom color map based on the output of an analysis routine from another python module. That type of workflow simply is not possible in VMD.