I would appreciate function for set customfield name for project scope in Custom Field configuration or Customfield context

For example scenario:

Problem manager has container Project problem and he need new customfield name "Problem start" so we created new date Customfield "Problem start"
Week later Test manager need new customfield "Test iteration start" in project Test iterations, but he wants exactly this name in screen...
week later Service Desk agent new customfield "Predicted resolution date" in project Service desk requests...

After 3 weeks we have 3 customfields in 3 separated containters, all of them are Date fields, not used in more than One exact project, because their name is so Unique, than nobody else can use them, because their orientation is for one specific use Case.

BUT

IF I could create customfield named: "Date" and set in Field Config schema or context his personalizated name for some scope....

We would have 1 customfield with 3 separated names for many usecases. 
There are BIG Jira implementations, where corporates generate customfields in hundreds (100 text fields in instance is normal...) but all of this is caused because manager need exact name on screen or export.

In architecture of JIRA, there is one conjuctive unique identificator and it is ID of Customfield, We can create many customfields with identical name and different type, so why I can not change Name in scope of project? or issueType?

Advantage: optimalization and performance of database
minimalization generation fields in Jira with one purpose...
reusing existing fields

Disadvantege: JQL name, export name orientation

nowadays I know workaround and it is Script runner Behaviour. But it is not solution, because many times I can not run JS on all screens and set up context. Export is with origin name, JQL as well.