i guess I'd say that, like setting up UFW, this is getting into areas that define what WordOps is trying to be and maybe I'm not clear about that. Personally, what I use it for, and want to use it for, is a fast, standardized way to set up nginx served websites, especially wordpress sites, using best practices.
I have my own general purpose ansible playbooks that i use to provision and set up VPS servers. Those playbooks set up UFW how i want it set up. They also set up SSH how i want it set up. So for me, having WO mess with those configs is a downside. i guess I'm not opposed to WO offering the capabilities to set up things like this for people, but my preference, as with the UFW set up, would be for it to be an opt-in option rather than a by default unless opt-out option.
but i really do think that you should decide what the boundaries are for what WO is trying to be. It's one thing if it's a utility for setting up websites (that's how i see it). It's a totally different thing if it's a general purpose utility for setting up servers from scratch. And if that's what it is trying to be, then I'd say there might be more to do than setting up UFW and SSH. my playbooks install all kinds of software, set up my shell and lots of dotfiles, install and configure SSH keys and SSH configs, set up SSH access to private git repos, set up private mesh networking, set up timezones and time sync, etc.
for me personally, if WO steps on stuff i already have configured, then I have to spend some time to guard against that and I'm not in favor of spending that time. If it is something that WO offers but doesn't force me to use, then I think that's great.
EDIT: oops i left this in my browser when i wrote it hours ago and posted it without having read the posts about it being a separate command. I'm all for that.