Ok, point taken. However, just hoping that noone will need more than a rather small number of entries is no solution either.
It doesn’t have to be scrollable menus, but it should scale up well also for a rather large number of menu entries, paths, you name it. For example, I am sure, somewhere out there, there is a user who would need a fifth additional VST path, but he/she cannot set one, because there are only four entries.
Such experiences can easily frustrate, and in the worst case, this user cannot use WL, just because, in his/her workflow and installed plugins, five paths are absolutely needed for whatever reason.
Such special needs are of course hard to foresee by the developer, and thus, it is always best practice to avoid such (more or less arbitrary) limitations whenever possible. Then, all users are happy, the ones with a single VST path (I’m using VST paths just as an example here) and the ones who need, say, 10 or 20 VST paths (to use a rather extreme value).