As long as I'm here, I'll discuss New Netherland Settlers as an example of the purposes of project-management and project-protection, and to provide some perspective on the kinds of things that do and don't require communication.
Many New Netherland people had an exceptionally diverse variety of names (both multiple names and diverse spellings of those names). To help bring order to a potentially chaotic situation, the New Netherland Settlers Project uses project-protection primarily to protect LNABs -- to prevent merges that change an LNAB that has been determined to be correct, and also to prevent merges that erratically change the LNAB before the person's correct LNAB has been determined. In this project, PPP should not be misinterpreted to mean the profile is practically perfect and should not be edited. In fact, many of the project's PPP profiles are in pretty poor shape. Often those profiles have been placed into maintenance categories that identify some of the types of improvements the profiles need. Those maintenance categories are supposed to encourage members to do the research or editing to improve the profile. (They are most definitely not a personal to-do list for the Project Leader!)
Members who want to work on New Netherland profiles (particularly if they want to create new profiles) should first learn about New Netherland and its naming practices, the project's naming conventions, and the limitations of WikiTree's search utilities, and they should expect to need to learn about sources for New Netherland records and genealogy. The project (meaning all of its members) can try to provide advice about these topics and others, but primary responsibility for researching a person's ancestors still belongs to the person who cares about those ancestors; having the project account on a profile as a manager does not mean that the project wants to take over that person's genealogy.
A project Leader does need to get involved any time that a PPP-ed profile needs a new LNAB or needs to be merged into another profile. When that happens, the member requesting the change should expect to be asked to document the evidence and reasoning supporting the change (or at least try to do so) -- don't assume that the project leader will do all the necessary research and add the documentation to the profile.