You're right on the money. The main win is in triage speed, not config time. Making one policy might save you ten minutes. Having a single log source when the store manager is screaming at 9 PM on a Friday saves you hours.
Don't just look for tabs. Ask for the exact log. Say: "Show me a log entry for a blocked connection attempt from a PoS terminal to the internet." That entry needs to show you the local interface it came in on, the firewall rule that denied it, the user/host tag, and the SD-WAN tunnel it *would* have used. If any of those data points are missing or live in a totally different log viewer, it's glued together.
The other test is to make a simple policy, then break it on purpose. Introduce a routing loop or a conflicting security rule. If you have to open two separate "diagnostic" or "monitoring" sections to see the full picture of why it's broken, the integration is skin-deep.