On the traces not being displayed:
@ihertzler, can you please share the tif image and the traces file with us (use e.g, wetransfer, or similar if you have problems uploading it here).
On the cumbersome shortcuts:
Commercial software is also affected by this. We all use software in different ways, and what some of us see as feature-rich options, others see as clutter, so things to need to be balanced. What about using just Alt? We could have it so that as soon as you press it, the fork operation starts. Would that work for you?
As a side note, for mouse-intensity work (such as tracing), having a mouse with programmable buttons does help. You can customize your clicks, and even assign keystroke triggers to them, for the ultimate customization. They are not that expensive nowadays.
On the da4 neurons:
Amazing cells. As large as a rodent Purkinje neuron! I traced several of those myself back in my Drosophila years! What you would need is a significant speed boost, not just customization tweaks.
How confident are you with scripting SNT? In the Script Editor, have a look at Templates>Neuroanatomy>Tracing> Reconstruction from Skeleton (Python) : It takes a thresholded image of a ddaC cell (File>Open Samples>ddaC Neuron (84K)) , and automatically converts the foreground into editable paths. Of course it makes mistakes, but the expectation is that curating such errors is significantly faster than starting a fresh. Here is how the it looks: original image on left, rendered traces on the right: