Custom Fields are amazing, but they have some limitations. The biggest one, for me, is that I can't make a field required in one form, but not required in another form. If I say the field is required, it's required in ALL forms where it is present.
A way to get around this is to create 2 of the same field, but now I need a way to identify which is which. So I could name one of them "Title" and the other "Title (Required)" or "Title (Optional)". But now there's a new problem: The user sees that name. So instead of just displaying "Title" to the user in both forms, now one says "Title" and the other says "Title (Required)*" (Since the system adds the * next to the required fields already.)
What would be nice, for this use case and others, would be for the fields to have a "Name" - the name by which the system identifies them - and a "Display Name" - the name that the user sees. These two names could default to be the same unless a different display name is set. This allows you to potentially have multiple fields with the same display text but different use cases, while also allowing admins to easily identify which is which.
This would also be useful for fields that could be entered different ways. For example, if you have a field called "Equipment" but have it as a dropdown in one form and text entry in another, you could name those fields something like "Equipment - Dropdown" and "Equipment - Text" while having the display name being "Equipment" on both fields.