Now this is a version of rest_query I can live with.  There is a master processing running that keeps track of the orgs and their access tokens.  When an org is registered with rest_query:register/3, a new rest_query process is started for performing queries for that org and that org alone.
This version feels much better.  The Org info needed for a query is stored with the process serving that org in loopdata.  Only the ets table is on an orgid => Pid mapping.  I also had to clean up server names as then weren't unique, neither were child names inside the supervisor.

I can now register 2 different orgs and repeatedly run queries against each.