Lots of questions about the new Adobe Web SDK (alloy.js) bouncing around. Corey Spencer answers those for you!

i wish you would have not edited this idea.  That way the history if renaming the satellite object and that being something that is not supported would still be here.   Im not a fan of revising comments and such.  

I would suggest posting an idea to cover this line from your first post, instead of renaming the _satellite object."My reason for wanting this is to allow a configuration where two or more Launch instances are deployed on the same page." 

Have you seen the reference implementation guides?  There is one for angular.Adobe Launch Reference Implementation Guides:  https://helpx.adobe.com/experience-manager/kt/integration/using/launch-reference-architecture-guides.html

This is not supported in any fashion at this time.  Please do not do this.

Let's back up a step here.  Create a simple page load rule and set an evar to a test value.  Let's make sure that Analytics car fire the beacon from your beta environment, and that we can see the beacon in a debugger of some flavor.

Just to clarify, you are looking at the staging library right?  As of now when I look into the account I do not see the rules as being published to production yet.

You can reuse variables but not in the way you are thinking.  Setup Data Elements within DTM to do this.  You can have a Data Element named "ProductID".  Then within analytics you set eVar1 (or whatever variable) to %ProductID% and then you can use that Data Element for any other var or tool or tag ...

Use the "Enters Viewport" event type.