Get changes of the parameterized pipeline on the fly in Jenkins
Currently what you are asking for is not possible. This is due to the way that the Jenkinsfile is loaded into the pipeline.
I think dolphy said it best on this StackOverflow answer (I saved this link a while ago to follow it for changes, because I had the same questions):

Jenkins does not know about the new parameters until it retrieves, parses, and runs the Jenkinsfile, and the only way to do that is to...run a build.
In effect, the build history will always be &quot;one run behind&quot; the Jenkinsfile; when you change something in the Jenkinsfile, the next build will run with the &quot;old&quot; Jenkinsfile, but pick up and process the new Jenkinsfile for the build after that.

There is also a related Jenkins Ticket you can follow