Tricky member benefit pricing rule advice wanted

We are upgrading soon to v16. After reading everything I could on how to set up member admission benefits as pricing rules, I find that our current setup doesn't exactly match with/translate to the way the new benefit features work. I'd love to get advice or suggestions on ways to accomplish a good setup!

The Tech Interactive is a science center with general admission, and members get free daily admission for themselves (number depending on membership level) and half-price admission for any guests. Currently, members have their own TNEW modes of sale that show just member adult/child tickets and guest adult/child tickets, not the full-price adult/child tickets. Individual and Individual Plus members get 1 or 2 free tickets total per day. Family-level members and above get free admission for 2 or 4 adults and all of the kids in their household. Even though in theory our Family-and-up members could claim every child in their party is part of their household and covered by their unlimited child admission access, we do sometimes see members purchasing "guest child" tickets.

Reading up on benefit pricing rules in v16, the recommended setup is a price type change rule that automatically converts selected tickets into member benefit tickets. However, this method assumes that all member-benefit price types (member adult/child and guest adult/child) are hidden, and the member selects publicly accessible full-price GA tickets that convert in the cart. It would not allow members to see both member child and guest child ticket options and choose some of each, because both of those price types would have to be hidden from the public view.

I also looked into the Enforce Limit pricing rule to remove some of the member adult tickets out of a member's cart and force them to select guest adult for the rest. However, the help system guide recommends using this only for events that are members-only, not for events like general admission that have a mix of public and member price types. And the price type used for an "enforce limit" action cannot also be used for a price type change, which would potentially mean having a mix of enforce limit member tickets and price type change member tickets on the same performances, depending on how each member level's benefit pricing rule was set up.

Please let me know if you see something I'm missing in how this all works, or if you can suggest a way to set up admission pricing rules to allow for the scenario I outlined above. Thanks!