How to manage O365 Group membership through AD Security Groups and/or nested O365 Groups?

We really need security groups to define members of O365 groups.... reason is simple logic: I would assume everyone would agree that there are a smaller number of expected security groups in comparison to the expected number of Office 365 groups...especially if we are going to be making O365 groups for small tasks/projects with the same list of members over and over again. O365 groups without relying on pre-set groups of individuals (security groups) is simply unusable at scale. For example - if you have 50 O365 groups for 50 different little projects and you hire more team member that will access these projects...you are stuck editing 50 groups instead of tossing that new person into one security group. The only way this works is powershell scripting - but it looks like you are at least partially adding O365 groups to prevent scripting (auto-creation of resources.) Right now it seems like O365 groups are in Chaos Mode...