Automatic screensaver enable after a period of inactivity is considered a fail safe control.

`caffeinate` can set assertions, the same assertions that Zoom or PowerPoint or Keynote do to stop the screen going to sleep during a meeting or presentation, the same assertions that the browsers can set during streaming video, so you absolutely can bypass whatever your admins set using `caffeinate -dmisu` which sets every assertion available.

It’s not about capabilities, it’s about policy. Willfully violating security policies is generally going to go over poorly.