Verifying a few things.....

The Impact rating of Critical or Recommended typically refers to whether the patch is a security patch or a non-security patch, with security patches being rated Critical and non-security patches being rated Recommended, as shown in the Content Report document I linked.

 CVSS score is separate from the Impact rating. It rates the severity of the vulnerability, as some vulnerabilities may have a greater impact or may be more exploitable. The vulnerability may require one or more patches to resolve it, most of which are likely to be security (Critical) patches.

 In general, if a Patch administrator applies Critical patches on a regular maintenance schedule he’ll take care of most CVEs. Likewise, if a CVE comes in, he can use its CVSS score (Low, Medium, High, Critical) to determine if he should apply the patches before his next maintenance cycle.

https://www.microfocus.com/documentation/zenworks-resources/ZENworksPatchManagementContentReport_AdvancedPatchFeed.pdf

So clearly our currently available method to meet escalated priority for those panic, 'patch now' problems, is all manual.  There must be a better way, automatable even, hence...  An Idea is born and in look of support to grow up to become a feature.  
Also have commented on the docs that should have a part of that clip you provided included.

I'm not sure why you would need anything manual.  Most just add All Critical Patches to the policy.  Make sure it auto-approves in short order.  Most don't have teams dedicated to truly testing patches, so they generally keep the auto-approval time low and with a low patch age.  Usually, at least a day since the worst of the worst patch releases will get pulled in that frame.  Be willing to annoy your users and force them to patch/reboot if those on high deem it a priority.   Some check on every refresh.....Some Check once a month....

Automating too many reboots does Not fly for most business.

Given the increasing rate of patches that have a nod at security (so that ZPM considers them 'critical') and need restarts, many businesses want to keep the system restarts to a dull roar and are content with a weekly window, but apparently random happening during the week is reserved for truly critical, such as that CVE's with a CVSS of over 9.0.    Tools that can't manage that simple requirement are likely to get replaced, as IT is the tail, not the dog. 

Currently, ZPM can only manage that manually, as ZPMs patch "critical" is not business critical, nor general InfoSec critical (I have a Discord chat going on this topic (vendor names withheld) at the moment, with a comment from some on this topic of "Sounds like willful ignorance to me... ")