You've misunderstood my question. I know 4.1 + 0.8.5 is verified and that the others are not. That's literally the point of and exactly what I said in my question.
So, why are they not verified? As your colleague @Amxx says here, Etherscan should recognise the clones and display them correctly if the implementation contract is verified, which it is in all my cases.
So, please can you explain why the clones are not verified under 4.2 even though the implementation is? This seems like a clear bug as it works absolutely fine under 4.1.