As it has already been hinted that there is going to be a performance settings menu in addition to the new safety settings at some point in the future, and that cameras may be on that menu, I need to bring up a potential issue. Up to this point, cameras have been used as a make-shift way of making stuff local only. In their current state, they are the only component that is disabled by default for everyone but the user of the avatar. This has been exploited in several ways. For example, you can have the camera output to a tiny render texture. You can then read that texture in a shader and check a pixel to see if it has changed from the default value of (0,0,0,0). If it has, you know the camera is active and the local player is the one rendering the shader. An example of this is I've used this technique to make crosshairs for guns that only show up on my screen. They would be very annoying if everyone could see them. A popular use of cameras is to make a HUD selfie camera that always shows the player's face. Nobody other than the player using the hud needs to render the camera (or the hud for that matter) as they will most likely never be able to see it.
If cameras behavior changes to have them on for all players by default with a performance setting to turn them off we are going to need a replacement. It would be great if you guys could add a script to make a gameobject and its children as enabled for the avatar's user only. That should fully be able to replace the functionality of local cameras.
Additionally, it would be nice if you could mark objects to not be enabled on the mirror copy of the player (I've run into several issues with objects on the mirror copy fighting with those on my main avatar) or possibly mark objects as friends-only.