@topbooster told me that it's not possible due to the type of HIVE SQL table. I've mentioned him there so more info can possibly be provided.
We're testing with comment upvoting at the moment and having issues there as well. Scaled voting doesn't appear to be working on hive.vote trail when the vote comments box is ticked. Is this something you've stumbled onto before?
I don’t use scaled voting, I believe the only usable solution is a dedicated account for each token.
I see. It's not been an issue with the trail when upvoting posts, just with the comments. If the post and comments can be separated for the data tables then we'll be progressing forward with a dedicated curator for comments/engagement (possibly using the fixed voting weight if this is the only usable solution at this time) and the curators for post content. Details still to be ironed out, potential issues highlighted are appreciated.
I've been speaking with @memeisfun who is running the @vyb.engagement project/account and he mentioned issues with scaled voting as well when using hive.vote.