I noticed this too. Hopefully this will be fixed soon.
Now, the User agreements screen does have the option to set consents on a policy by policy basis and it includes a filter to show 'Not agreed' so this indicates the logic is there in the background to track non-consents (although it is unclear if it distinguishes between 'consent refused' and 'not yet consented' which it should.)
You can't withdraw consent yet in the latest version of the plugin, which is required, so they will have to add that feature as well.
What I would like the policy tool to do is allow the DPO/admin to set some policies as 'consent required' and the others as 'consent optional'.
Granted a user may be required to consent to the primary purpose just to use Moodle, but for policies for other purposes you must have the option to refuse consent initially or it may very well not be valid consent (per recital 42). The DPO needs to be able to make that decision and have it set up accordingly.