Sorry for the delay! Happy to report that tbl-expand in dynamic tables (in Shiraz by @Mohammad) is fantastic if you hack it to follow existing view & edit cascades.
Find this shadow tiddler:
$:/plugins/kookma/shiraz/macros/dtables/tbl-expand
And replace its contents with the following:
\define display-expanded-record()
<td colspan=<<ncols>> class="shiraz-dtable-expanded-record">
<$tiddler tiddler=<<currentRecord>> >
<$list filter="[<tempTableEdit>getindex[mode]match[edit]]" variable=ignore>
{{||$:/core/ui/EditTemplate/body}}
</$list>
<$list filter="[<tempTableEdit>getindex[mode]match[view]]" variable=ignore>
{{||$:/core/ui/ViewTemplate/body}}
</$list>
</$tiddler>
</td>
\end
Before doing this, I also imported @TW_Tones cascade tweak here; I’m not sure whether that was necessary to making the whole package work smoothly.
Honestly, I thought it was going to involve some cascade-specific learning curve (beyond what I already was doing in the control panel for regular story-river purposes). Nope! The cascade action happens “behind” the core view and edit templates. Brilliantly simple.
@Mohammad — this strikes me as a pretty straightforward default behavior, no?
If someone’s got custom view and edit templates for recipes, or contacts, or tasks, or whatever, all of them should now just work when they’re accessed within a dynamic table. 
PLUS: Side benefit: if you edit within a dynamic table, you’re not editing a “draft-of”. This is convenient when your corresponding view template invokes the tiddler’s title in a filter (such as a dynamic table with [all[current]listed[]] condition) — within the expanded dynamic table row, you can keep the edit preview pane open, and see your changes “live” in the preview pane — as they will appear with the corresponding template applied.
-Springer