Battery Capacity (mAh) counters as sensors vs attributes

[Ne0-Hack3r]

I've created custom sensors to provide battery capacity data (Full vs Remaining) for DP, D2, D2M in a form that can be recorded, accessed in History, and more easily integrated on the dashboard. I realize many may not care about these particular readings but I find them informative in terms of understanding calibration and also observing when the full capacity counter, in particular, is altered (this is particularly strange for DP at times).

In any case, I was wondering if there are better ways to handle the data while continuing to have it as an attribute (of the main battery level, for example) or if there is interest (and/or willingness on the part of @tolwi) to consider having these as actual sensors rather than attributes within the integration itself. I'm also interested to know if there are particular reasons this data was treated as attributes in the first place.