No, it's not relevant to this discussion at all.

Hardly, because it's not about scrypt itself but about how (according to the author) the library's API encourages incorrect usage.

A reader of your comment might assume that the article is about some perceived flaw in scrypt itself.

I can see that perspective. I could have made it more clear.

I see it as it being more about incorrect usage or application, rather than a fault with scrypt.