Could a factor, value or similar be beneficial in UnitConverter?

[keilw]

Implementing classes like AbstractConverter contain methods like Optional<Number> linearFactor() which most subclasses use for its getValue() numeric method. The MultiplyConverter interface defines a getFactor() method also returning that value by default. So while it is a string in a few cases even there a numeric factor or formula of some kind exists, thus would it make sense to expose this value in future versions of UnitConverter?