Yeah, I know what collision means

Looks like they are now focused on private keys bruteforcing but, as they stated, finding collision is among LBC priorities
That's what they're doing, as you can see in the image, it's about "
private key collision" and not an address collision which is the topic is all about.
OP is asking about address collision which is two different private keys that produce the same pubKey hash.
LBC on the other hand, is specifically looking for private keys in 2^160 bit range that's already used by others, same address but same private key.
If it's about address collision, they wouldn't only search within that weak private key range.