>>6Keep in mind, D-Bus is not only an IPC system; it also includes lifecycle tracking, service activation, security policy, and other higher-level structure and assumptions.
The best place to start is to read the D-Bus tutorial, so you have a concrete idea what D-Bus actually is. If you understand other protocols on a wire format level, you may also want to read the D-Bus specification to see what D-Bus looks like on a low level.
As the tutorial and specification both explain, D-Bus is tuned for some specific use cases. Thus, it probably isn't tuned for what you want to do, unless you are doing the things D-Bus was designed for. Don't make the mistake of thinking that any system involving "IPC" is the same thing.
It should be possible to bridge D-Bus to other IPC systems, just as D-Bus can be bridged to object systems.