Summary: If a resource is registered to a local repository (one with a URL starting with "file://") and you do Find-PSResource it searches through all registered repositories, even if it finds the resource in the local repository early on. Additionally as a result if the resource is registered to multiple local repositories this will cause the cmdlet to return multiple repositories. This is inconsistent with how the cmdlet acts for remote registered cmdlets and takes significantly more time (performance concern).

To replicate:
mkdir my_test_module`` New-ModuleManifest -Path ./test_local_module/test_local_module.psd1 -Description "a test"
Register-PSResourceRepository -Name "psgettestlocal3" -URL "C:/Repos/testdir3" -Priority 30
Register-PSResourceRepository -Name "psgettestlocal4" -URL "C:/Repos/testdir4" -Priority 25
Publish-PSResource -Path .\test_local_module\ -Repository psgettestlocal3
Publish-PSResource -Path .\test_local_module\ -Repository psgettestlocal4
Find-PSResource "test_local_module"

returns multiple resources as so:

I ran Find-PSResource "test_local_module" with -Verbose and -Debug switches and it shows that for local repos it starts searching repos in order of which has highest ranking priority first, searches in psgettestlocal3 and psgettestlocal4 (without printing a module could not be found in repository message but keeps searching through all other repositories registered.