Is it a good idea to crank up the settings in Argon2id to max (20 iterations, 100 length, salted) for applications? I’m new to the cybersecurity subject, but I assume keeping the hashing as slow as possible (and a longer hash length = fewer chances of collusion) helps fight against brute-forcing. Is that correct?

Also, what is the security of having a password logging in system that: 1: Uses the max Argon2id settings, to make the authentication slow 2: Makes it take 1–2 seconds (in a circle loading style) for it to either fail, or succeed 3: Adds a 1-second cooldown, increasing by 0.5s by every failed attempt (any successful attempt in that cooldown is ignored, it just says that it’s on cooldown nevertheless)

I’m open to suggestions! (I’m not implementing everything, but thought experiments are a good place to start, IMO)