it is easy to run multiple instances, but as tom notes, only one driver per instance.
using a service to augment data works well in some cases, such as adding data from some one-wire sensors to the database that has data from your weather station.
but for multiple weather stations, or for power monitoring, tide monitoring, water consumption, fuel consumption, air quality, or other types of data collection, it is often better to run multiple instances of weewx.
you can always combine data into a single report with a separate, dedicated skin and wee_reports. or you can aggregate by feeding into influx or emoncms or something that feeds off of mqtt.
this is how i typically configure a system that will have multiple instances of weewx on it:
/opt/weewx-x.y.z - weewx is installed here
/opt/weewx-skins - skins go here
/etc/weewx/ - configurations go here, one per instance
/var/lib/weewx/ - database files go here, one per instance
/etc/init.d/weewx-multi - script that starts/stops them
/etc/default/weewx-multi - list of which instances should run
that way i can test new releases of weewx without disturbing what is already running. i can test/update one instance without disturbing the others. i can update/test skins without disturbing whatever is already running. i can update skins independently of weewx itself.
on most systems i run only two or three weewx instances, but i have a couple of systems with 6 or 8 instances.
m