DP ovh also depends on the total # of kangaroos. And the total # of kangaroos depends on how many GPUs you use and how many kangs / GPU (you may have different GPU specs, some more powerful, some with less or more kangaroos to increase throughput to maximum).

Why? Simple, let's say you have 1000 GPUs all running at once, each jumping 1 million kangs.

So even if one lucky GPU jumps one lucky kangaroo to a DP that is later found to be a collision, there were still 999.999.999 kangaroos that were also each jumped the same amount of times as the lucky kangaroo, on the lucky GPU and on the other 999 GPUs.

If one really plans to break 135 there are much more factors in play in order to determine the optimal parameters to minimize the total runtime, and I'm not only talking about the command line parameters, but the kernel code itself. RC's software is just a proof of concept about his strategy, it doesn't take a genius to figure out his actual code is totally different and most likely heavily more optimized so that it fits well with his algorithm.