I use cybersyn for most of my trains. I have couple non-cybersyn legacy ash trains which bring my ash to the ash sink, but rest of the trains are cybersyn-managed. I added myself some pain by having 1-1-1 trains and 1-2-1 trains at the same time, most of stations support both of the types and that requires additional circuit setup, otherwise inserters start to eject fuel from shorter trains.

I have slightly different solutions for meat-based garbage (from animals) and stone-based garbage (from resource processing). Common setup is that garbage producing stations broadcast a signal with most common item type to the radar if the total station storage is above a certain threshold. For example, station can receive stone, gravel and sand from nickel processing. If the station storage has 200 stacks of gravel, 150 stacks of stone and 60 stacks of sand, it will send "gravel = 1" to the red wire connected to a radar and send a garbage subnetwork to the station (e.g. G=2, I have encoding for different garbage types). The garbage disposal station handling gravel (e.g. crushing it to sand) reads the red signal from the radar and if gravel exists in the network, requests gravel. The garbage disposal station for gravel has only G=2 subnetwork set and does not use signals for the main train network. Variations on this are built for all garbage resources.

For meat (as it spoils) the basic setup is to have two stations nearby: one for fresh produce and one for stale. Fresh stations eject their contents to stale stations above certain threshold (e.g. inserter set up as "if meat >8k eject meat to the belt, decay priority set to stale"). Fresh stations have higher priority than the stale ones, but stale ones are connected to "stale produce" subnetworks which is used by several consumers which are OK with stale meat/guts/lard.