The Where Used table considers the configuration specification defined in the filter criteria. That means, if latest is defined as criteria, only parent assemblies in LATEST will be displayed
The affected object collector in Change Tasks does consider the configuration specification criteria concerning the collected objects. This leads to collecting also non latest objects
In use cases e.g. mass changes (replacements) a potential high amount of wrong (non latest) data would be collected. In order to being able to perform the mass change, users would need to revise the collected objects (if the parts are already released). This results in error messages and the user has to identify and finally to remove the non latest parts from the affected objects table
As the current system behavior has been classified as Enhancement, I am requesting it as a Product Idea. I am aware of workarounds like using the Where Used Table, selecting, copying and finally pasting them all into the change task, nevertheless the object collector is such a helpful and supporting tool so that an improvement regarding the described behavior make it even more efficient.