I think your use case actually is quite particular and uncommon. Keep in mind that Limesurvey was designed as a survey tool and mostly with this case in mind. It can be used of course for other things, like your test scenarios, but as you can see, specific demands seem to be different to the "research world". So what for you might seem to be a very normal, common requirement, for me and many others that come from the research part look odd and not a very relevant use case.
Good thing: Limesurvey is open source and you can always see if it makes sense to implement this yourself (or find someone to implement it for you). Of course you would need to check first, if this is something that could be implemented in the LS core or if it is rather something that needs to be in a plugin. Of course it would make sense to discuss things like that with the developer team first, because they might not want to implement it into core, as it might not fit well with the general purpose, etc. I am no developer to evaluate the impact of such a change on the core of LS.
Good thing: Limesurvey is open source and you can always see if it makes sense to implement this yourself (or find someone to implement it for you). Of course you would need to check first, if this is something that could be implemented in the LS core or if it is rather something that needs to be in a plugin. Of course it would make sense to discuss things like that with the developer team first, because they might not want to implement it into core, as it might not fit well with the general purpose, etc. I am no developer to evaluate the impact of such a change on the core of LS.
