Transaction Log need greater than 1500 rows

I notice that the Transaction Log query is only limited up to 1500 rows. This is significantly insufficient for doing back outs as although it does not happen often; there are instances whereby

1. users have done a load via a T.I across months

2. did data loads over the course of a day after they notice that they have loaded to either the wrong version overwriting correct numbers

3. Users notice that what they did 1 or 2 weeks ago was wrong and want us to reverse what was done as they may not have the original loaded templates to reload everything again.

4. Situations whereby users request admins to do a CLEAR ("C") on a high level and if a mistake is made, we have to quickly back out. A mistake is rare but it has happened and a 1500 limit is impossible to use. a "C" on a high level parent is usually a few thousand datapoints to tens of thousands of datapoints.

Most of the time, these datapoints are significantly more than 1500. It is usually a few thousand rows OR most recently there was a situation when I had to back out urgently an entire year's worth of wrongly loaded data which was about 150,000 rows. I am unable to break it down to smaller units of 1500 rows if I had to rely on PAW and I had no architect. 1500 row limit is way too little for my organisations needs and a limit of say 15,000 to 20,000 is more reasonable and something I can work with for identifying and backing out data based on elements that i can easily filter. I hope IBM can relook and reconsider the Transaction Log limit up to 15,000. I understand that it may not be ALL but it has to be way way WAY more than 1500.