I think restricting configuration editing to administrators and interface administrators is fine. I think restricting to intadmins would be too much right now; I view the use case for intadmin restriction being execution of code on other machines which I don't believe is the case here. This seems similar to other site configurations we allow any administrator to edit. If things change or it turns out local admins are making a lot of bad decisions, then maybe further restriction is worthwhile, but as it stands the permissions seem fine.
Topic on Talk:Growth/Community configuration
Hi @Wugapodes -- thanks for checking this capability out, and letting us know that it seems on the right track.