One might not.
Let me explain:
Most of the problems I’ve mentioned here (no tall of them) were due to some questionable UI choices, which in turn makes the “User Experience” a bit poor.
“User Interface” is how an app or a website communicates visually with its user, it’s a language in itself.
I would like you to fire up any other app you have and if you found a greyed out property then try and edit it. You will instantly realise that it’s a no-go for editing and that’s how the app is communicating this information with you. Not only apps but you can sometimes find that on web forms too, for example, if a web forum doesn’t allow you to change your username. It’s a common UI practice.
The problem here is not only that you have a greyed out property that a normal person would think he just can’t edit ( due to common practice ), but also it does not get exported when it’s obvious that it should ( because it’s placed where every other similar property does), which is a huge red flag from a UI/UX perspective, hence why at first I thought it was a bug and was massively surprised when I realised that it is how it’s supposed to work.
One simple way to solve this is by having the property greyed out and uneditable of course, but also have some sort of a radio button beside it and when the user clicks on that radio button it would change to the normal font and color, then the user would know that this property is now activated. Also, in general, every default property whether greyed out or not should be exported because that’s also what a normal person would expect I can also provide some example of that if needed.