It seems feasible to do this, but you would need a way to keep track of which query is which. I see some irony of wanting a table of queries to be used on tables, though. If you have that many queries to keep track of, this might not be the way you want to do this.
Case in point. I found myself writing functions over and over again, simply changing queries and tables affected in each function. A good example of this would be an html table full of checkboxes, or a dropdown list based off of a couple of columns in a table. So, I rewrote the functions to take the table name and columns as passed parameters. By generalizing the function and forcing more parameters to be passed, I cut down my coding significantly.
I guess my point is, instead of storing multiple queries, try to store the structure of the queries instead and pass the table and column data as parameters.
Hopefully, this might be of some help.