"While the libunity API is stable, the DBus protocol underneath is not. We strongly discourage anyone from relying on it" -> That pretty much does it. Unless Canonical changes its policy and provides a stable D-Bus protocol, it is not going to get integrated upstream.
Adding a new dependency is annoying but acceptable. However, if libunity uses libdbus directly, it is almost certainly not compatible with usage within libvlc. Getting libdbus to work right in a threaded mainloop-free application liek VLC is hard. The only code that integrates libdbus correctly at this point is VLC's own D-Bus MPRIS plugin.
"While the libunity API is stable, the DBus protocol underneath is not. We strongly discourage anyone from relying on it" -> That pretty much does it. Unless Canonical changes its policy and provides a stable D-Bus protocol, it is not going to get integrated upstream.
Adding a new dependency is annoying but acceptable. However, if libunity uses libdbus directly, it is almost certainly not compatible with usage within libvlc. Getting libdbus to work right in a threaded mainloop-free application liek VLC is hard. The only code that integrates libdbus correctly at this point is VLC's own D-Bus MPRIS plugin.