Parenting GO's to a ScrollRect canvas. Any downsides?

Hello everyone. I've recently been experimenting with new ways to use the new UI system, and I've figured out a way in which to make a scrollable game-screen. By that I mean, setting up a level with physics/gameobject (side-view) and enabling the camera to freely move around it by click-dragging or touch-dragging.

I've done this by creating a main canvas and adding a scroll-rect canvas which is scaled to cover the level dimensions, then parenting all the objects in the scene to the scroll rect canvas. This seems to work really well and saves a lot of unnecessary touch input coding (although there are screen size differences that would need to be worked out for scaling).

So my question is, would there be any ill-effects of doing this? The only downside I've found so far, other than the scaling is that gameObjects inherit Rect Transform properties (without showing them), so the transform values are vastly different. It doesn't seem to effect physics or rigidbody properties.