This is good, sort of.
Git looks at remote information for these local branches, and not vice versa. That is, the remote branch does not have multiple local tracking branches. Multiple local branches have the same remote tracking branch.
When you pull, it retrieves the corresponding remote branch, updates the corresponding remote tracking branch, and merges it. Everything will be fine; only one branch and its tracked branch. I suspect this is your real precedent.
When you click, usually the tracking information is not used at all. The default push.default value is matching , i.e. Push local branches to remote branches of the same name. In this case, everything will continue to be normal, trivial.
However, if you set push.default to tracking , it will again look for the correct remote branch for each local branch, but if your local branches are not identical, they obviously cannot be pushed there! Perhaps if you think that several local branches are monitoring the same remote, you simply do not want to set push.default to monitor.