If you directly access the Tablo NIC interface and set a static address inside of Tablo, and then you change routers because YOUR router died and the new one uses a slightly different IP scheme, say 192.168.1.0/24 instead of 192.168.0.0/24 which happens now and then, then what? You can't get to the Tablo because the IP is stuck on a network range that your new router isn't configured for and you have to change your new router before you get to the Tablo.
I see zero issues with a reserved IP in the router. It's pretty easy in quality routers, even fairly cheap ones these days and ensures that no matter what happens on the rest of the network, Tablo can be found or seen or accessed.
Most routers are smart enough to not assign a DHCP address that matches a static address.
Maybe of those you've seen, but I've seen quite a few higher end systems still assign an address if the device doesn't respond instantly when queried. I still see occasional "IP address conflict" messages on systems I work with.
IMO, address reservation is the best for most home networks, even some business cases (networking is what I do all day for a government agency)
It avoids hassles connected with other network device changes.
Even some of our LAN-to-LAN connections are based on reserved addresses as the ISP was for a while constantly building out their plant and addresses kept changing but we couldn't go pure DHCP as our base router allowed connections only if the outside IP addresses of the remote routers matched our profiles here.
We do STATIC for most servers, switches, many printers and routers as those need to be entered into DNS as static for multiple reasons beyond the scope of this forum. Our workstations or PCs we use in IT are on reserved addresses, not static.