You're right. For a usable symbol, each pin should appear in exactly one section, not repeated across multiple overlapping groups. The pin-grouping guidance is explicit that every pin on a complex IC should belong to exactly one sub-symbol/section, and the grouping should use the most common primary function for readability rather than listing every alternate mux function

So the cleaner rule is:

For this module, I would assign pins like this:

Because pins like:

…but for symbol organization, you normally pick one dominant bucket only. That matches the recommended practice of assigning each pin one section and one sub-symbol instead of duplicating multifunction pins across categories

If you're building the part in Flux, I’d use these sections:

If you want, I can next turn that into a clean pin property table with:

with no duplicated pins at all.