Yea I realized that only after. I agree it's slightly different from the grey text in text fields, but it still illustrates the point because it's also an implicit default value (that happens to be unchangable in this context). So it kinda applies, but yea not quite the same.

inherited versus default, that is kind of splitting hair when we're talking about user interface.
Here the gray means "this is what it's going to be if you don't write something else here"

Being shown what's the default isn't the same as having it actually in the field. For example the default might change, then these values would change with the default. There are also cases where they are inherited or something similar, where the upstream value isn't as fixed as defaults normally are. So there is a functional difference to showing you a greyed out default and actually having that default be in the field.

Especially for things that essentially are a web interface for a config file where the config file gets larger with values that aren't needed (this includes both NPM and Proxmox, as examples). Instead of like 3-4 lines it could now be like 20. It also becomes unclear when looking at the values later if they were actually set to that value intentionally or if it just happens to be the default that got filled in because some UI was used that filled all fields with their default values.

Showing the default outside in a label or as a tooltip-hover is an option, but has implications for the space needed and readability. And this way is actually much clearer if you want to look over a config and you need for example the default port or something, it's in the exact place you expect it, shown in grey to make it clear that it wasn't set intentionally but that it's just the default. In some UIs there's room for defaults, in some not. I personally vastly prefer them to be shown like this, as you might have guessed already.