This is the way I run it too, but there are a couple situations mqtt might work better for some.
One would be you need mqtt outside home assistant. It’s a very light weight and standard protocol that is used by many different home automation services.
This poster makes a good case too that since mqtt is a bit more universal, you don’t have to worry as much as version api schema conflicts between the home assistant integration and the zwave js addon.
Recently, there was a version conflict where the addon and home assistant weren’t updated at the same time, causing users to lose control of their zwave devices. Those using mqtt were not impacted by this.
The nice thing is that even if you dont need mqtt now, it’s a click away from enabling it in the future if you need it.