TomasK

You must use the "Warning" severity for the desired Web control rules to send the data to ESMC. However, be careful to not use it for rules that allow or block too many urls or it may have adverse effect on perfomance of the ESMC server if many clients start to send a lot of data.

If you want only accessing of one category of urls to be reported to ESMC, it should be fine. The problem could be if you created a rule for every single url with the Warning severity. Since a single client could generate several such records per second, with hundreds or thousands of machines reporting them to ESMC could cause network and server performance issues and congestion.

Per your changelog, is this already a known issue in v7.2 or different? Please explain this confusion.
This did NOT happened on any of our computers that has v7.2 installed.
another 2 weeks means Windows 10 computers that are "stuck" with ESET v7.2 can't be upgraded version 2004 of potential BSOD issue (https://support.eset.com/en/alert7506-windows-10-version-2004-bsod

Any ETA for the fix to be released?

Greetings! 
Listed as fixed in 7.3 "An on-demand scan launched from the ESMC console could shut down the computer even if this post-scan action was not selected" is exactly what started happening after I've upgraded Endpoint clients to 7.3. Never happened before. 
The process C:\Program Files\ESET\ESET Security\ekrn.exe (WKST-VRN-BKP01) has initiated the power off of computer WKST-VRN-BKP01 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Other (Planned)
 Reason Code: 0x80000000
 Shutdown Type: power off
 Comment: Computer scan completed
That comes from scheduled scan policy (daily on-demand scan with post-scan action set to "no action"). All upgraded endpoint clients have been shutdown after this scan.
Fix it please!