This is indeed an interesting problem, but very difficult to reproduce.
I *think* this is a glitch and hashcat while changing from one mask to another (in your case to or from mask number 1592 of 91133) it's not in sync somehow and thinks that the val > max because the mask before the current/new mask had a different max restore value etc... This is just an educated guess, because I saw a similar problem reported on the forum before and it also didn't make much sense and wasn't really reproducible easily.
If somebody could somehow generate a reproducible test mask file which always leads to this error, that would be great and much easier for the devs to troubleshoot and hopefully fix.
I *think* this is a glitch and hashcat while changing from one mask to another (in your case to or from mask number 1592 of 91133) it's not in sync somehow and thinks that the val > max because the mask before the current/new mask had a different max restore value etc... This is just an educated guess, because I saw a similar problem reported on the forum before and it also didn't make much sense and wasn't really reproducible easily.
If somebody could somehow generate a reproducible test mask file which always leads to this error, that would be great and much easier for the devs to troubleshoot and hopefully fix.