Indeed, we've run into this as well. That change made it into an early iteration of our next update. If you wind up having issues with the wrong service provider getting referenced, it should be safe to expose the provider in the editor so you can manipulate it manually as well.
In later revisions of our update branch we've exposed a public LeapProvider on the HandModelManager (formerly known as the HandPool) that allows HandModelBases in that manager to get a unified provider. I expect having control over custom provider usage will be easier when the next Core update drops (we're working on it! 
)