Request Timeout field in Crowd appears to do nothing?

While reviewing Crowd, I tried different values for both HTTP and Crowd specific Request Timeout and only the 0 value appeared to affect Crowd (would cause seemingly endless attempts to reconnect on a "bad" username/password).
I asked the team what this field was supposed to do to clarify I was testing the right thing and it was inferred I should create a ticket for review.

I tried values of 60, 1 and 20000 (in case millseconds regression) in the field. I tried with Crowd off and valid username/password as well as Crowd on and "bad" username/password and it immediately gave me a validation no matter what configuration (except in the 0 case).
I tried less combinations on the fallback general HTTP values but my findings were those are not being picked up either.

Investigation appreciated. If not just me, all the above should probably be (re)tested once a solution is implemented.

I did not check older NX3 or NX2 to see if working/not working at this time.