Generic Resources - Team Assignment Pool Yes or No?

Our On-Prem Project Server environment was set up with Generic Resources marked "No" for Team Assignment Pool. It seems we would want this to be a "Yes", so that tasks assigned to a Generic resource would be visible by Project Server users with the same role, and those users could then self-assign those tasks and provide updates. Our generic resources are meant to represent a "pool" of people in different labor categories, so that we can look at potential areas of under or over utilization. It seems that marking them as a Team Assignment Pool would reflect our intended use. For most of our generic resources, we don't plan to replace them with a specific person (such as production work). However, for some resources such as engineers, we would like them to be able to self-assign tasks and give updates in Project Server.

Is there a particular reason to keep our Generic Resources marked "No" for Team Assignment Pool? Does changing to "Yes" affect their capacity, availability, or Work/Cost values?