Please don't post duplicate questions; I answered some of this in a separate thread but will repeat it here.
clipping_threshold relates to derivative truncation.
chunk_width is because we train on fixed-size chunks of data, it's the number of frames per chunk.
chunk_left_context/right_context is the number of frames of input we give per chunk, to the left/right of the parts with labels (it's additional context to the LSTM).
label-delay has the same effect as putting all the labels 5 frames later than where they appear in the original system's alignments, so the LSTM gets to see further in the future than it normally would (this makes it less asymmetric, since it would normally see infinite left context and zero right context).
lstm-delay (or the delay=x parameter in lstm layers in xconfigs), controls the recurrence period of the LSTM. Negative, IIRC, means a forwards-in-time LSTM, and positive means a backwards-in-time LSTM (it's badly named, it's really the opposite of a delay). Values of +1 and -1 mean standard LSTMs; with (e.g.) -3, it's like having several separate 3 chains of LSTMs, each with a recurrence period of 3 frames.
Regarding splice_indexes and num_lstm_layers: splice_indexes relates to splicing frames together in TDNNs, and num_lstm_layers is the number of LSTM layers, probably in a setup where some layers are LSTM and some are TDNN. But both of these are only used in setups with outdated scripts. The latest setup will use the 'xconfig' mechanism which is much clearer.
I don't recommend to tune any of these things for now. The only thing you should possibly tune is the cell-dim (and for projected LSTMs, there are two other dims which should generally be one quarter of the cell-dim).