This is highly dependent on how you look at the thing. Two possible outlooks are attacks you can do right now on stock hardware (typically with GPUs), and what attacks you could do if you had the right kind of custom hardware. As far as I can tell Argon2, being explicitly designed to be memory-hard, is very much tailored to the second one.
I’m also sceptical about the timing based threshold (one second). Computers are a bit faster now than they were in 2015, so there’s a chance that threshold now lowered. I understand why they used that easy to understand shorthand, but it’s unlikely to age well.
One thing everyone do seem to agree on though: Argon2 is stronger with long enough run times, if you can tolerate them. Maybe you don’t if you’re running a server under fairly high login load, but maybe you do if you use some augmented PAKE (say OPAQUE) to offload the expensive computation to the client.
I'm not an expert, but I'm really curious to hear more. It's especially weird given I've heard nothing but good things about Argon2 otherwise.