Seems like AsyncWorldEdit Premium version really does things in a weird hackish but also very logical way, allowing the developer to code for Bukkit, Cauldron, Forge and whatever-else. Due to this, AA wasn't able to discover the owner of the /awe command and was failing its conflict checks.

This has now been fixed thanks to the amazing @Ac3dUd3 who helped me to debug and provided valuable feedback. Thank you, dear Sir, you have saved our days

------------------------------------------------------

Version 1.53
=============
New maintenance version.

Added:
* new /aa_debug command added to operatively (i.e. upon calling this command) enable/disable debug mode. This mode can be used to provide more information to the plugin author when needed (for example when something in the plugin breaks). There is also a "debug" config option to turn this mode on/off by default upon plugin load.

Fixed:
* /aa_checkcommandconflicts now works with the latest version of AsyncWorldEdit
* /aa_checkcommandconflicts will now correctly show conflicting commands for WorldEdit when other plugins (namely AWE) are extending its functionality