I think you should be worried about it, because it will be pretty frustrating if you commit to a particular design decision now and then later discover that it’s not going to work when it comes time to distribute the app.
The bottom line is that you should never write any code that depends on the name of any class, property, or function as a string. Part of the production build process makes the code bundle smaller by silently transforming named things to have smaller names.
The template shouldn’t ever hear about any of this. What I would do is to write good old *ngFor="let hero of heroes" in the template, and do all the magic populating heroes in the backing controller. I think you might be able to adapt this two-level select example to your situation, as it is effectively swapping out the choices available for one select based on choices made in another.