The snmpcollector_hub_metapackage was intentional since we were constantly needing to update it for new versions of packages (ppm, etc) and this was causing confusion to clients and support.
Also in the past, snmpcollector was seriously linked to specific versions of ppm and it's required probes, discovery server and a few others. The metapackage(s) were a response to that problem.
The probes are all supposed to work with older versions. At this point so it isn't so critical to keep the versions lock step, and thus the need for version-specific metapackages was not as important.
If the customer was using this package for the convenience of deploying the probes like alarm_enrichment and NAS/etc, we might suggest they could create their own metapackage for this purpose as we will no longer be maintaining ours.