Changing the mechanism is possible in a future update/hard fork, but for now we're kind of stuck with it as-is from a practical point of view (development resources, schedule, etc.)
The effort here to somewhat improve the function using a second layer approach is helpful. Not ideal necessarily, but better than nothing for now.
RE: SBD Potato Day 50: NEW Conversion Tracking API & DAO Proposal