I totally agree that it's less than optimal to set up patch names in the environment, and would love an easier solution.
You can search around online, as you've noticed, and find some things, but not everything, and an editor or importer that helps you quickly and easily create one would be great. Not holding my breath for something like that though.
These things should come with Logic (as with most other DAWs)
That's a tricky statement, because it's dependent upon which hardware you're using, and which DAW you're using. Some DAWs will have instrument definitions for some hardwhere, while other DAWs will have instrument definitions with other hardware. None of them have all of them.
With my hardware (Roland JV1010, MC307, XP60... Yamaha RS7000... Korg Z1), Cakewalk Sonar had all of them except the 307, which was easily found. Setup was straightforward once I figured it out, though not easy, particularly where expansion cards were concerned.
With the same hardware, Logic Pro doesn't cover the bases as well, and Cubase was flat out useless.
Even still, I see this same complaint over on the Sonar forum: "Sonar needs to come with instrument definitions for 'XYZ' synth."
So, while for me Sonar was excellent for this, for others it's flat out useless.
However, there are other ways to get control that are in some cases more useful than Patch selection. Patch/Performance selection is great when you're scrolling through presets or saved user presets, but if you've tweaked the performances and patches, and are out of memory space on the hardware, there's no equal to sysex messages.
Since discovering sysex, I'll likely never use patch/performance instrument definitions again.
But, yes... I agree... it would be nice to have better coverage.