copied roles shows all security context vs seeded roles shows only applicable security context

Summary:

Custom roles created by just copying any seeded role (e.g. General Accountant) shows whole list of Security Context in "Manage Data Access for User" whereas corresponding seeded roles just populate relevant applicable security context.

What is that which is restricting poping up of only applicable security context on "Manage Data Access for User" FSM task.

What is the way to restrict security context LoV to only applicable ones.

Steps to reproduce:

Create a custom role (**** General Accountant) by coping any seeded role (e.g. General Accountant) and no chnages to privileges/ Duty roles/ Data Security policies etc.

Assign both the roles (seeded one as well as custom created one to same user.