I am assuming you are looking for an out-of-the-box solution, and I have not seen this, but you can do a couple of workarounds to get your purpose with a box solution.
You can always look at the log journal which should have a full description of the process
Out-of-the-box manual solution
- CREATE a seed file or container file where you load all your families in the native version, in your case, 2016.
- EXPORT the families to address any issues. You can do a simple export; this process will stop in families with problems or issues to be fixed

3. IDENTIFY & FIX the families individually and reload to the file ( the process will stop when encounters a family with an issue take note and fix it and then reload )

4. OPEN the seed file in a newer version (the recommendation is to do it one version at a time. In your case, 8X painful, I know!) I would suggest doing it in 2 steps: 2016 to 2018 and then 2018 to 2024, to identify the families with issues and fix them as you go.
5. Check your journal file for more data you can use dynamo to gather this information

You can visualize the journal with a creative workflow, since it is a text file then use Python + Jupyter to parse and convert the information (data) to Excel file and then you can visualize in a PowerBi

RVT to the max