What kind of conflicts do you have? If you cannot register the same shortcut in both of them simultaneously then it's expected that only one of the gets the control over the shortcut.
myself to answer in details.
But I can say from my previous experience with kglobalacel from kde4 vs lxqt-globalkeys:
pros of lxqt-globalkeys:
* less dependencies (apparently it's a draw with kglobalacel from kde5)
* different action can be linked to a shortcut: client call, dbus call or app launch
* multiple actions can be linked to a shortcut (wider possibilities including shortcut shadowing, prioritising and so on)
cons of lxqt-globalkeys:
* editor for dbus call binding and app launch is still in progress
* daemon still depends on QtDBus+QtCore (I have plans to get rid even from this dependency - then we'll be able to use the daemon in lxde with gtk clone of editor)
I wouldn't drop lxqt-globalkeys just because there is kglobalaccel. We can make lxqt-globalkeys optional if we need any moment later.