You can't ignore ranges completely because bitcrack is not designed so. If you start an offset for each GPU working point, things will awfully slow down ...
You have to adjust the initial point generation, remove the first point doubling kernel and adjust the result reporting slightly.
Everything else can remain almost untouched and will not influence performance.