Well, yes and no. No because the link should likely not be there. Yes because this is actually expected:
As said, alias-clients were implemented for those who really need it but we haven't had the time to code the proper interface nor do more involved testing (what you did now) so somethings are expected to work suboptimal at the moment.
Thanks for testing this, however, I don't see us making another v5.x release (unless we have to fix a bug in a v5.5.2 patch release), as v6.0 is right on its way. Hopefully, we can open a beta round sometime this year. The v5.0 beta period was very productive as well. And as reward for testing, things can get implemented very quickly during these periods (I know you benefited from this as well 
).
But, hence, I'd like to postpone further work on alias-clients for now. It is not even clear how settings will be stored in v6.0. We'll likely store them in the database instead having to deal with setupVars.conf any longer, but that all is very much undiscovered and will be explored once the API/web interface came its way.