Maintainer of the "Inheritance Project Plugin" speaking here, which was the reason for this workaround.
The root-cause has been fixed on our side, and the code from the plugin has been aligned with the code from LTS 1.596.x.
We are currently preparing the full release of the updated plugin, which should arrive within a week (wk.26/27). It took longer than expected to move all of our internal plugins from 1.509.x to 1.596.x, which has significantly delayed upstreaming the complete set of fixes into the OSS community.
We sincerely apologize for the delays and the resulting necessity for this ugly workaround in the Jenkins core.