I haven't used dbus very much, but I get the impression it's just another means to expose interfaces except that you will have a daemon running ready to answer the call. The main benefit I see here is that you might keep certain initialized context in memory (if the calls are not spaced out too far apart in time) instead of saved to disk as any cli interface tool could do to maintain state across calls. For some uses, having a way to keep info in memory across multiple process calls (avoiding read/write to disk and temp file management/cleanup) could provide a great reduction in latency.
I could be way off about what dbus provides. As usual, I'm always excited to be clued in and learn more about anything related to Linux.