I’m slightly more paranoid and less so when it comes to gadgets and what’s easy to deploy (low cost tech with short installation service calls) vs really secure. So I may not be the right person to chime in, but I know enough about breaking technology and what bad actors do nowadays to know you mitigate risk knowing things will fail and you should be highly confident that experts say it’ll function in life safety moments. Life Safety Systems MUST be certified to rely on them. Don’t mess with them. Supplement them with a parallel system. And, stop reading now if the remaining post is going to send you into a fit of paranoia. 
I HATE professional systems that aren’t hardwired. I had to argue with ADT at my last place because I wanted the “more obsolete” system because the installer didn’t want to run wires in a professional manner. So I paid more for a system that always worked, without visible wires. That didn’t depend on batteries that weren’t changed on time or who’s power supply fluxated between a cold unoccupied house and one that’ was warm and tosty in the winter.
Trusting radio signals from devices comes with variables I won’t count on - be it WiFi interference, “cycling” questionable appliances or electronics, or normally “coexisting” z-wave systems (like your hub and the alarm panel) that run into issues when one or the other has a busy moment. How many times have we had a device report not make it back or an automation trigger properly?
Many of these things are improved or resolved by Z-Wave Plus or LR devices. With that, my trust?? or rather tolerance means I do rely more on them for secondary purposes.
Deciding how your critical system reports back for monitoring is important as well. Many IP and VOIP systems have not been deemed reliable enough to become life safety certified. Cellular notifications, hardline backups to IP based solutions are smart for mission critical. Both still can and have failed.
Don’t trust cloud-based solutions. I’ve toyed with a now-bankrupt cloud automation provider, and another that finally is doing more local after swearing by the cloud - until they failed miserably. Find a hub (my father uses ZBox, I use Hubitat right now) that is 100% off-cloud (or optionally cloud-extended) for better reliability. There are dozens of factors outside your or your vendor’s control that could cause your cloud-based system to fail in a critical moment.
I currently use Nest for my smoke alarms (until they expire as it’s EOL) but check out PLACE as my current advanced alternative. While you’re likely integrating via a Cloud API (open or psudo-closed), there’s a plethora of information a good device can supplement with your automation system. Build a parallel notification system using something like the ZEN 55 as @getoffmylawn and @Barkis did.
Now, throw in the fact that we have modern burglers that scan for and clone your car’s proximity key all while standing outside as you get your well needed sleep. This tech isn’t obscure, so unless it’s a random smash and grab, your burglar probably uses a radio frequency jammer and makes the effort to rip out your cable or fiber internet openly mounted on the side of your house. 
Just like locks, this stuff keeps your average “good” person from breaking in. And, a home automation that turns on lights and unlocks doors when the smoke alarm goes off, or starts flashing all the lights in the house when a contact opens will probably do the job of alerting you and making your house less interesting to rob. It’s really about adding another layer on top of that “certified” system, and both are better together than no system. If somebody’s willing to stand by the liabilities with life safety device certifications, use their system. Some even have extra open/close contacts you could put a zwave relay on to detect and report burglary to your home automation system. Don’t fit your home grown device or hack in to the core system if you depend on it. Build next to it.