I think this could be a bulkwalk problem.
Can you compare if you do a
snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.43.8.2.1.13
with
snmpwalk -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.43.8.2.1.13
If the normal walk don’t work you can only disable the “printer_input” check for this device.
Look for the rule “Disabled checks”.
Good news for the v3 context problem. Inside the code for version 1.7 this looks like already removed and there should be no problem anymore with the original problem 