Hi Raphael,
From what I understand, this code filters draft records based on user permissions. Commenting it out would likely mean that drafts would be visible regardless of your user permissions. It may also cause errors, as it appears to be a variable that is used elsewhere.
I did notice one of our developers filing a bug today that sounds related to what you've described. See:
It's not exactly the same issue, but it may be related.
Unfortunately, there are also a number of known issues with user permissions. I suspect that there may be an issue here with inheriting the view draft permissions to lower-level descriptions. I haven't had a chance to test this myself, but one of our developers says he tried and was unable to reproduce. That said, without knowing exactly how you've created your group, it's possible we just haven't properly reproduced the necessary steps. When I have some time, I will try to reproduce this issue myself.
In the meantime, I will say that it's become quite difficult to fix individual bugs in the permissions module, because the entire module is very old, and needs to be fully replaced. Many of the issues stem from the inheritance model used in the permissions, meaning problems upstream can be carried downstream, and it can be difficult to debug without starting in an entire rewrite - something Artefactual can't undertake without community support. So far we have not found any sponsors willing to undertake this work.
I'll let you know if I learn more.
Regards,