The easiest way to confirm is just unpublish that LDAP plugin. Save a user where their params are fine. After save see if there's a problem. If not then you've found your issue. Reviewing your LDAP plugin at a glance it seams to be doing its own user object construction, binding, and saving. There is likely something going wrong during that process. Probably below.
github.com/ShMaunder/JMapMyLDAP/blob/056b899dac16bcaf124bf228af0a683cda662bd4/libraries/shmanic/adapter/event/bouncer.php#L370
During onUserAfterSave the user object is reconstructed, silently saved, and the original user object remapped. Can probably comment out line 370 and 373 to quickly check if that's where it's going wrong, but there maybe other usages throughout the plugin.
If i remember correctly it is not possible to disable params field.
Can't be unpublished but can be set to not display on registration and/or profile edit. However doesn't sound like that's the case for you.