In my experience, administrators care most that the needed software and settings are applied to a machine. They care less about how the software and settings got applied. It could be via bundle, manually, or with a 3rd party tool.
They want to know whether or not the software and settings are there.
Enter, the Device Requirements Policy!
This policy simply contains a set of system requirements based on the current ZENworks system requirements framework.
These policies would be assigned to applicable devices as determined by the administrator.
These could also be made into sets of Device Requirements Policies and assigned as policy sets.
The assigned devices would regularly scan to determine compliance with the assigned policies.
There would be reports and dashlets to show the administrator the current compliance with the policies and policy sets.
To bring the devices into compliance, the administrator could create a bundle or bundles to make the needed changes.
The bundles would be assigned to the applicable Device Requirements Policy instead of to the devices themselves.
The bundles would follow the need for compliance allowing the administrator to set and forget once he/she knows the bundle works.
In short, the Device Requirements Policy allows the administrator to report on software and settings compliance in a way that can be directly and automatically acted on.