How to avoid the FNDLIBR run and bounce of managers when new programs are added/deleted to conc comb

For Combined rule changes (for example in future, if any new programs are added to combined rules or removed from combined rules):

Customer need to run:

FNDLIBR FND FNDCPBWV apps/<apps password> SYSADMIN 'System Administrator' SYSADMIN

and bounced managers (at least the Managers that includes the combined rules and Standard Manager).

Test case executed in EBS instance for this:
1) Included "Active Users" in "Month End Jobs" Comibned Rule -> Ran "Acive Users" and it was executed in "Standard Manager"
2) Bounced "Month End Mfg Manager" -> Ran "Active Users" and it was executed in "Standard Manager"
3) Ran FNDLIBR command -> Ran "Active Users" and it was still executed in "Standard Manager"