We state this in our TAG:
"ThinLinc has a feature where sessions against Windows Remote Desktop Servers are distributed among several available hosts. In order for this to work, the tl-loadagent service must run on all Windows servers."
Which is not true, regarding that a deployment of RDS on 2012r2 and 2016 requires a session broker, which is in it self a load balancer of session between session hosts in a RDS cluster. Actually, ThinLinc loadbalancer operation will end up in a no-op in such environment.
I like the new paragraph much better than the old one. Makes it clear that the administrator has a choice between what Windows provides and what we provide.