Default project task code/number in Requisition based on expenditure type or transaction controls

Summary:

Transaction controls are enabled in our production environment. However, users are presented with all available task codes on the projected when populating the billing section of the requisition. Allowing selection of the project codes outside of the transaction controls causes significant frustration for more casual/infrequent users.
Can any mapping be applied to ether default or limit the number of task codes displayed to requesters

Content (please ensure you mask any confidential information):

Is there any advise on limiting the project tasks displayed to users? It would be ideal to limit the tasks presented to users based on the transaction controls we have set within the business.