Forbidden password multiple list with independant verification mode

Hi,
Could you allow us to create multiple lists of forbidden password with their own verification mode?
Actually there is only one list and we've to chose between exact match and contain parameters.

It could be great to use both because it's different use case:
Exact match is perfect for weak and very known password like Topsecret, 1234567890 etc.
But contain need to be used to prevent people from using some bad pattern like Company@CurrentYear! / Devolutions@2022!

Another great addition should be a strict restriction preventing the validating an entry with a forbidden password.
So if someone try to type one of them, it can't validate the credential. It might sound exagerated but in our personal usecase it will force the engineer to set a good one on the target then in DVLS.

Best regards,

Arnaud