I could hack my scope to 150 MHz at a later date, once I need to get higher than 50 MHz, under which I currently work, but one best be clear about the sampling artifacts that occur even at 100 MHz.
The threads discussing it are all over eevblog. You can overcome the input filter, but the sampling and memory length are still the same, whether its a 50 or 150 MHz scope.
See discussions and threads with posts by rf-loop, jahonen and others. I think rf-loop is also instrumentvu and posted this over 2 year ago:
What is basically shown is that 100 MHz on a single channel on a 100 MHz rated 1102E, providing 1Gs/s is already tasking the scope, you can see the sine wave wavering about at 100 MHz, and its from a Fluke scope calibrator at that, so the signal source is good. When he switches on the second channel, it worsens, since the Rigol goes into 500Ms/s. Then he switches on long memory length it drops to 250 Ms/s, at 2.5x the Nyquist frequency, and finally turns off sinx/x and watch what happens. Why he got any negative comments for such a clear response baffles me. My guess, its a language barrier thing.
What is shown won't change if you hack the scope to 150 MHz, those are real time sampling artifacts. So if you do, even at 100 MHz, the basic 1000E hardware with 2 channels the scope is really best to 50 MHz at the default memory depth, and with long memory, its down to 25 MHz.
Since I have an unmodded 1052E, I have reproduced rf-loops issue by switching on 2 channels with long memory, which turns the scope into 25 MHz, and looking at say a 40 MHz sine wave and it gives the same goofiness as the last images on the youtube link.
The good news is you can overcome some of this by using equivalent time sampling, which isn't shown on the demo, so long as you are measuring repetitive signals. But if not, one should be aware of these limitations.