Of course, but:
1. I do not participate in the puzzle race:) For fun, not more.
2. Optimal amount of DP (for 135 and higher) is much more than we can collect and save in RAM.
3. You can start Mark1 with different DP bits, amount of DP, different jump size (k parameter) and others.
4. And I have gpu code too, but it is boring.
And by the way, 135 and higher are like a lottery ticket.
Yeah, having FTL GPU jumper's boring.
There's absolutely no need to store DPs in RAM, let alone a bloom filter. That requirement is needed by BSGS's "fast memory lookup", but for DPs this is an "offline" step, and it's conceptually either an "insert this DP" (because we want to store a DP, of course) or "the DP could not be inserted" (collision, yay) op-code. So, basically, a storage database. A bloom filter is useless, and fast lookup is also useless, for this scenario. Kangaroo requires zero memory (except for the current point), in its essence.