- Better emission/reception : the sonoff can be located anywhere in a location that can be better for zigbee reception, in particular far from USB3 port from the raspberry (interference in the 2.4Ghz ISM band), and closer to endpoint Zigbee devices (more centralized)
- Better emission/reception : the sonoff is designed to reduce interference between its internal wifi and zigbee transceiver
- The sonoff can handle far more devices (more than 100 i think) than the CC2531 (less than 20) can. Altough there is other dongles that can handle that much (check zigbee2mqtt project for details)
-line of sight is 80meters on sonoff vs 30meters approx on CC2531 (same remark for other dongles as above)
- the sonoff can handle local rules and the soft is very reliable (the tasmota software is one of the best quality software i've ever seen) without using central program such as domoticz / jeedom / openHAB / Home Assistant that may have bugs (sorry for all developers of this programs

Zigbee2tamosta support in domoticz would be a great feature. It's s shame that the zigpy library could not be integrated which may be a good way to integrate zigbee within domoticz. I saw the discussion about an obscure crash related to sqlite3 usage, maybe i'll take a look closer to see if i can think about a elegant solution about dynamic /static linking against the sqlite3 library.
Note about using rules on tasmota to modify payloads to get them work on domoticz : this is really a bad way to go, because number and size of rules is very limited (ESP8266 have little memory). Rules should be used for other tasks such as extending the the direct associations permitted by zigbee for example. Node-Red can be a workaround (transforming MQTT message) but quite heavy for the job.