The cited EULA terms don't depend for applicability on creating an account, only on accessing LinkedIn. Whether or not that's enforceable and in what jurisdiction is a different question, and not one that's relevant here; unless OP is extremely foolish, we are not about to see that question tested again in court.
In any case, LinkedIn accounts are clickwrapped in the EULA, and you can't build a scraper for stuff behind their auth wall - which, I believe as a direct response to LinkedIn vs. HiQ, is more or less everything they serve - without being able to get past it yourself. So the question of whether or not OP has agreed to the EULA, which LinkedIn complains Browserflow is marketed in part to violate, isn't remotely germane to a meaningful discussion of the issue.
In any case, LinkedIn accounts are clickwrapped in the EULA, and you can't build a scraper for stuff behind their auth wall - which, I believe as a direct response to LinkedIn vs. HiQ, is more or less everything they serve - without being able to get past it yourself. So the question of whether or not OP has agreed to the EULA, which LinkedIn complains Browserflow is marketed in part to violate, isn't remotely germane to a meaningful discussion of the issue.