As far as I understad it based on :
https://github.com/jenkinsci/lockable-resources-plugin/blob/lockable-resources-1.11/src/main/java/org/jenkins/plugins/lockableresources/LockableResourcesManager.java#L288

Its actually the releasing job who queues up the next job. Also the controlling inversePrecedence comes from the job thats releasing the lock, not the job who is getting the resource from the last job.