I tested and reviewed patch #2 and it works correctly.
Tested and review patch #16, it does the job correctly.
I tested and reviewed Patch #8 and I can confirm that it's solving this issue.
Patch #7 and #8 working correctly, Thanks.
Patch #3 looks like a great solution, patch works perfectly.
Solution #3 is working for me, also patch #4 working correctly.
Patch #4 working for me.
Patch #5 working for me.
Currently, we check only if the user has 'update' permissions, so I created a simple patch.
First, it checks if the user already has a profile created for the current profile type, if no then it checks the 'create' permission if there is a profile then it checks the 'update' permission. I am not sure if this patch will break some other functionality but for this use case it definitely fixes the issue with few lines of code.
Patch #4 tested, works perfectly.
Patch form #3 works perfect.
Indeed, we first need to add "Vote Result "Count" for content items" relationship and then we can add sort criteria -> Value (Desc: The numeric value of the vote.)
I tried to reproduce this issue with this and also the newer version of the module but it works fine for me. After reviewing the module's code and after I did some debugging I came to the conclusion that the part where the content is reassigned to an anonymous user (or whatever else we choose in "When cancelling a user account" field) is done in the drupal core, not in this module.