Currently lockable resource purpose is to detect overlap of resource using. It's a wonderful feature and is intuitively CI pipeline tool responsilble and removes need for external reservation dependecies.
Another external dependency is (probably) needed for telling what configuration paramaters resource have which impact build or test automation execution. That would be included to lockable resource. I suggest to give environment variables to build use from locablre resource.

Eg. configure lockable resource to have value
CONNECTED_MOBILE_PHONE=5
And using Jenkins build has e.g. environment variable
RESOURCE_CONNECTED_MOBILE_PHONE