Glenn Stanton

some basic thoughts:
1) if an effect (FX) is used only for that instrument - most times you can just put it on that track (either in the FX bin or using the Pro Channel) as it's not being "shared".
2) if there are several instruments of a similar kind, those would benefit from being routed to an aux track and/or a buss. e.g. i have several acoustic guitars, or several percussion instruments - like a drum kit - those may benefit by routing those to an aux track or buss and then applying reverb there, or have a dedicated shared reverb buss you can send multiple instruments to.
3) route the instrument tracks and aux track and busses to the master buss. 
so:
track + eq + reverb ---> master buss & send to "room" reverb
track + eq + reverb ---> master buss & send to "room" reverb
track + eq + ...FX...   ---> master buss & send to "room" reverb
room reverb ---> master buss
master buss ---> IO output
you can also have drums with their own reverb as a set as well as say the snare having it's own (common)
track + eq + snare reverb ---> drum buss & send to "room" reverb & send to "drum reverb"
track + eq ---> drum buss & send to "room" reverb & send to "drum reverb"
track + eq ---> drum buss & send to "room" reverb & send to "drum reverb"
attached is a block diagram of my template which may be useful for you to study as well.
DAW template - 02 - mix.svg
 

ah yes!
set timeline to millisecond, then place the markers to align on clips etc - helps to define the spacing, then just drag in the timeline from marker 1 to marker 2 and you can read out the duration. in the example 00:00:14.732 between the 2 markers (ignore the now time)

in my folder - the module has been renamed as ".old" -- maybe i did that when it was buggy?

 
 

maybe create a new track and make it mono, then drag, or otherwise load up, the same effects and see if they cause this behavior. for more tests - make it stereo and load up the effects and try to make it mono.   or perhaps it's not only the first, but any stereo on a mono track causing this?

hmmm. worked for me - once i set it to extreme and put snap to grid to 1/4, 1/2, 1/8T etc all snaps were, er, extreme in aligning to the grid... what version are you running?

in general, the native meters in the "red" do not necessarily indicate clipping etc. so if your RMS level is good and you're seeing peaks in the red, you're probably ok. of course you can calibrate by running a sine wave and testing the levels and seeing if you're able to identify where you have clipping due to RMS being too high.
from: https://www.soundonsound.com/techniques/establishing-project-studio-reference-monitoring-levels

 
also: if you want to check voltages etc. https://vintageking.com/blog/2016/07/calibrate-converter/
i'd suggest using a K-level meter or similar (i use) Izotope Insight. but i also use a master limiter (Waves L3 or Cwb PC Limiter) set to -1db peak and maybe 2db gain reduction max. this provides a decent level and still retaining a lot of dynamics even with the occasional limit getting hit.

it's usually a balance of the thresholds, but with anything automatic, you're letting a computer make the decisions - I recommend you make a copy of the audio clip(s) so you can tweak them later... you could use the take lanes for the copy and then do any "comping" and make adjustments where the remove silence was too aggressive.

another option is to use Melodyne to strip out noise artifacts or Izotope RX-7/8 to "fix it", and/or gate/compress it (or even all of the above).