We are not rejecting anything. We are just saying, if you could pass on data from the token table of an anonymous survey to the response table, Limesurvey could not claim that it is "technically anonymous". Because you could pass on an ID that clearly identifies a person, their name, their email address, etc. Thus the text that LS displays for anonymous surveys would be misleading.
What you are doing is basically to bypass the measures of an anonymous survey in Limesurvey and while the information that you are passing on might not be "dangerous" itself, it could be. Thus I find the impression of technical anonymity that you present to your respondents through the fact that your survey is labeled as "anonymous" rather misleading, because with the same bypass, you could also send a personal ID to your survey.
Actually, I think I will propose that anonymous surveys in LS should not accept external URL parameters, because it could lead to people saying that anonymous surveys in LS are not really anonymous.
Now, don't get me wrong. This is more a technical thing and something that I think Limesurvey needs to check, because it is not good if we give the impression that the survey is technically anonymous and you can bypass it that easily, if you are malicious.
What you are basically doing is what I described here, and which in my opinion is perfectly fine, if you explain it in the right way and don't say that there is no technical way to connect personal data with responses, because obviously there is:
So technically the data is not anonymous, because people could connect them if they want to, but in practices the personal data was treated separately and thus analysis was anonymous. However, with this approach you can NOT claim a 100% technical anonymity. You need your respondents to trust you.