This is an Argumentum ad Populum. Just because JRiver does it too, it must mean it is correct to do. That is a VERY weak and fallacious argument. Look, the EBU (the creators of R128) document that describes the “Loudness Range” measurement says this:
“Loudness Range should not be confused with other measures like dynamic range or crest factor, etc.”
In other words, it is not meant to be used as a dynamic range number because it is not a dynamic range number. Yet that is exactly what Roon does. Uses it as a dynamic range number. What JRiver does is irrelevant. Roon is misleading because it is representing the number as dynamic range when it is a number used for loudness control in broadcasting.
In that thread you said was a valuable read, you effectively said that the crest factor-based number DR uses provides you with meaningful information while the R128 number is misleading. What I read from Roon “devs” was justifications for using that number over the crest factor DR Database number. What you wrote was spot on and what the devs wrote is an effort to justify a poor choice.