Hi,
thanks for starting the discussion! 
I’m working as a consultant and often do installations and trainings for customers. Most customers are confused when creating and managing resources at the beginning because of taxonomy complexity (e.g. created a hostgroup in the wrong context). Beside the Host/Content Host separation, most customers told me that they find having multiple organizations and locations too complex at all in the beginning.
I totally agree with this. I’m also using Uyuni/SUSE Manager quite a lot where you only have organizations as top-level taxonomy - most customers find this easier. I have no customer that makes use of nested organizations and locations. It’s a nice to have but I don’t see a common use-case.
Most customer installations I do look like this:
- one Foreman/Katello host
- one Foreman proxy running Pulp (for larger installations where I want to keep the Pulp load from the main server)
- Foreman proxies per remote locations (if required)
Usually remote locations have a dedicated location in the same organization. Most of my customers don’t require dedicated organizations for multi-tenancy - I only had a few installations where this was needed. Most resources that are shared between organizations are network and DNS information - not sharing resources might be a drawback for some users, I think.
Just my 2 cent - might not apply to bigger customer sites. Hope this helps a little bit.
Best wishes,
Christian.