The way some command verifiers work is to set the value of a command history parameters in a custom command post-processor. Then a verifier can use it to match command responses.
We may implement the ParameterToSet option at some point but I see an issue with it being used the way you propose: if you have two pending commands both setting the same parameter, they will overwrite each other's value.
Unless we do a trick and set a command history parameter similarly with what the post-processors do - those parameters are contextualized to the particular command sent so multiple of them can coexist in parallel.