It seems counter-intuitive that even when specifying a custom workspace you might still get one appended with a suffix such as "@2".

Could there be an option either at the Jenkins or job level to disable using the lease workflow when using custom workspace, so that we can guarantee that we get the workspace specified?

This is the behavior we've come to expect that was default in AbstractBuild.