My assumption is that "Windows Universal Volume Control" is synonymous with "SMTC" (SystemMediaTransportControls), since SMTC can be used to read the information that foobar2000 reports. I'm not sure what you mean with misleading, the setting name indicates to me it integrates with Windows to report what it's currently playing and that's what it does, just with some missing information.
Anyway, I've gone ahead now and forked the old foo_mediacontrol plugin, compiled it using the newest foobar2000 SDK and added reporting of the current timeline position and song duration.
You can find the source code and binary releases here: https://github.com/ungive/foo_mediacontrol
This is what it ends up looking on Discord if you use Music Presence
In my personal opinion foobar2000 should be fixed to report the additional missing information, so a plugin like this becomes obsolete.
This is what foo_mediacontrol reports with my changes:
AppUserModelId: foobar2000.exe
Title: Closer
Artist: The Chainsmokers, Halsey
AlbumTitle: Closer
PlaybackStatus: Playing
Position: 14865ms
Position (live): 189885ms
LastUpdatedTime: 1728647744095ms
StartTime: 0ms
EndTime: 244960ms
EndTime - StartTime (duration): 244960ms
MinSeekTime: 0ms
MaxSeekTime: 244960ms
MaxSeekTime - MinSeekTime (duration): 244960ms
And this is what foobar2000 with "Windows Universal Volume Control" reports for that song:
AppUserModelId: foobar2000.exe
Title: Closer
Artist: The Chainsmokers, Halsey
AlbumTitle: <empty>
PlaybackStatus: Playing
Position: 0ms
Position (live): 13373121716571ms
LastUpdatedTime: -11644473600000ms
StartTime: 0ms
EndTime: 0ms
EndTime - StartTime (duration): 0ms
MinSeekTime: 0ms
MaxSeekTime: 0ms
MaxSeekTime - MinSeekTime (duration): 0ms