I agree with your conclusions. However, the poster I was responding to was suggesting that the category of "int" necessarily excludes non-decimal representations in the same sense that the category of "stone" excludes "paper".
I think in this case it's not parseInt that's at fault, it's the fact that map optionally passes additional arguments.
I think in this case it's not parseInt that's at fault, it's the fact that map optionally passes additional arguments.