The interface is a string array, so the user can populate it however they want (I would do it like the above too).
One additional comment: I'm personally not a fan of providing the name of something in more than one place. If ignoring controls on the front panel is common (and I'm guessing it actually isn't very common), then I would prefer if the template included a for loop which iterates over every control reference given to it and extracts its Label.Text property to use as the filtering array.
Of course, since the default is to have no control, this code could be in a disable structure, or you could feed it one of the built-in controls, which I assume is meaningless, since it filters them anyway.
However, I am happy with the template as this is really an edge use case I exposed.
I actually use it to filter the default template controls etc... (otherwise LabVIEW crashed when it tried to write the tag refs to disk using OpenG ) but this is all done internally in the engine.
One example I can think of is that it may have to do with localisation?
...it doesn't really make any difference if you do add all controls since who expects a control on a preferences dialogue not to remember what you put in it?
Using an Indicator to display a piece of text (e.g. like a decoration/title that's constant) as opposed to using Free Text.