The issue with the older switches and dimmers is that they don't report physical changes. As long as you are fully automated, the lack dwindles to nearly nothing. BUT if you base automation on the physical movement of a switch or dimmer, then that status is not sent. It's not a Hubitat created problem, it's a Lutron one because they owned a patent that scared many of the big vendors and they created devices that didn't send status. That patent expired AND the ZWave creators found another way. Thus ZWave Plus is the answer to a question you might not have. And you can always decide to buy just ONE to go in that super critical spot.
SmartThings worked around it by Polling Everything, needed or not. Hubitat created a ZWave Poller app that allows you to select specific devices to poll. The obvious problem is that polling eats away at the mesh speed. The 'holes' between ZWave packets are reduced.
SO.. two things, one, determine if you require physical change to drive automation. For a lot of people, they want those switches showing on Dashboards and that demands you poll. Again, think hard about this. 
Decide if there's ONE that might be a candidate for replacing and use that antique in a spot you always wished you could automate, but just wasn't worth the bucks.
Two, similar, if you only have a few devices, polling isn't going to eat so much time that you'll notice, clearly SmartThings polls a lot and no one complains, but the cloud latency hides it. We all just blame the cloud and not their poller.
Underlying all of this is that Hubitat opens opportunities to expand -- what people around here call 'the rabbit hole' and you will likely find you want to add devices and automate more. I've been using Hubitat for more than 2 years and I added a new device just yesterday... so, yea, addicting.
