boomerbubba, I commend you for such diligence on the various TOS.. I should probably put it on the to-do list to allow wards to disable the Google Map if it makes them feel uncomfortable.
On that note, that's generally been my development process for YouthMaster (and other projects) -- release a v1, then take notes on suggestions over the course of a few months. When time permits, develop and release a v2 incorporating the bulk of the new ideas and suggestions.
I plan to carry forward in that same manner -- so v3 (release 3?) will include an option to disable/enable the mapping tool.
I also like the idea of 11yr old scouts (I too was an 11 yr old scoutmaster). The system currently allows "anyone" to register, so 11 yr olds can get in, they just won't show up on the "Deacons Scout Progress" page. It will be very trivial (< 5 minutes) to add a separate link to "11yr Old Progress" and just filter on any males < 12 yrs. That could either be a v3 feature or a quick addition if someone really needs it.
As far as "Faith in God" -- that's never been in scope, and my knee-jerk reaction is to push back. I believe a lot of software applications become bloated and loose any hope of being user friendly due to the amount of screens, options, buttons, checks, features (the user eventually gets lost in the UI). I firmly believe in KISS (Keep-It-Simple-Stupid). I fear if I move into "Faith in God" then "PrimaryMaster" and "EldersQuorumMaster", etc, will be the next ones knocking at the door. I'd prefer to keep the focus on youth (12-18) with 11 yr scouting as the exception. .... All that said, I used to make the same argument about adding YW/Personal Progress, and finally caved

So who knows.
Finally, on the complicated mix of wards/troops -- the scenario you described sounds like a nightmare to translate into proper use cases. I'm sure it is possible (anything's possible) from a technical standpoint to develop the code to support your scenario, but what would it do to the codebase in terms of complexity and maintenance going forward? As an already supported solution I'd offer you the option of giving the various troops/segregations their own instance of YouthMaster. (i.e. Ward1-Troop1.youthmaster.org Ward1-Troop2.youthmaster.org, etc). Then you'd need Ward1-
YW.youthmaster.org. Unfortunately, the segregation would diminish the value of tools like the Send Email and Maps which really need everyone in the same database -- but at least for tracking requirements and EditGrid spreadsheets you'd be in good shape.