POI database handling
I have been testing and trying the early versions in beta since a year maybe. And the mechanics of association by naming convention is still working, which is good. And POI search was only an explicit user function.
Now, in addition, with the feature going into official PRO version, there is an automatic presentation of tons of POIs when you use the Locus-provided maps as a base. I do share the concerns I have seen in other comments, critizinging that there is no control over amount and type of object to be shown.
I fully understand you do not want to invest science to improve here. But a few simple things would help:
1) in the list fo POIs allow to restrict to the perimeter of the map currently shown. Not hard, as you know and show the distances to the map center already. To make things trivial, just take the radius of the enclosing circle around the map shown as the inclusion criteria. Zero confighuration, all on the fly. Currently selecting huts e.g. will fill you a list fo 100 elements, incl huts being 50 or more than 100 kms away. My suggestion will allow to assemble relevant POIs of different kinds without accumulating 100s of them in the selection.
2) Maps like OpenAndroMaps are really great and I typically use them. But POI handling then is totally disconnected - you have a long list of available DBs, that is all. But you already have this "fast map switch" mechanics; just employ it to the POI DBs as well. Currently you show a full list of .DBs you found after startup. Simply offer the 5 or so nearest to the map center. Same way you do for maps themselves.
3) No science, but a great user support would be "profiles", defining a subset of POI types to be shown. That is somewhat more work for sure and may be beyond the limit of your current investment of time.
Besides that I wish you and family a nice Xmas time and all the best for upcoming 2015.