you can't change the iteration count (cost settings) without making the hash uncrackable. Therefore, technically you could change it, but it won't crack for sure with wrong settings.
btw. you didn't mention what your settings are, is it 5 (=> 2^5 = 32) too ? pipe in theory could change the speed a little bit, but if the password generator on the left side is very slow or the hashing algorithm on the right not slow/hard enough, the speed might be a little bit slower than expected.
btw. also do not forget to use -w 3 or even -w 4 to reach maximum speed (like the default settings in the benchmark are using) ... and for other hash types that do have both pure and optimized OpenCL kernels (NOT applicable for bcrypt), you should also use -O (again, not needed/meaningful for -m 3200 = bcrypt)
btw. you didn't mention what your settings are, is it 5 (=> 2^5 = 32) too ? pipe in theory could change the speed a little bit, but if the password generator on the left side is very slow or the hashing algorithm on the right not slow/hard enough, the speed might be a little bit slower than expected.
btw. also do not forget to use -w 3 or even -w 4 to reach maximum speed (like the default settings in the benchmark are using) ... and for other hash types that do have both pure and optimized OpenCL kernels (NOT applicable for bcrypt), you should also use -O (again, not needed/meaningful for -m 3200 = bcrypt)