Unfortunately this type of analysis while simple to do, is not correct with respect to the amplification requirement. Or true dynamic range needed to avoid distortion.
The main issue is measurements of dynamic range. The meter used in these databases which gets its data from Foobar plug in, is based on a plug-in that PMF designed years ago (now defunct). You can read about it in the internet archives:
http://web.archive.org/web/20130317013741/http://pleasurizemusic.com/en/our-aim
Here is the key aspect:
View attachment 126038
In plain English the meter is designed to find very short-term dynamic compression in music with a real-time meter. It does not at all as it indicates, give you the *max* dynamic range for an entire song. As a trivial example, if I have 30 seconds of silence and then 30 seconds of sine wave at full value, then I have as massive of a dynamic range as the format allows. In 16 bit format, that would be 96 dB! A short-term peak to average meter would show 3 dB which is the peak to average of the sine wave.
A much more accurate analysis is what
@solderdude has done with grabbing different segments of a track and plotting the amplitudes in a storage scope. Then you know the real dynamic range for that segment of music. You would then have to repeat that for the whole track and of course for your entire library for that matter!
One catch is any digital silence. Such like above example, huge exaggerates dynamic range so you need statistical analysis to find and remove these.
I cover most of this in my recent video on dynamic range:
So while I admire the effort Erin put in to outline the whole process of a quick, back of the envelop computation, it unfortunately does not produce the proper answers for this application.