chop and friends work under the hood by triggering the sound once for each 'slice', but with different
end parameters. These parameters are ignored by MIDI, so instead you'll just be triggering sounds multiple times, a bit like 'ply' I guess.
jux works by applying
pan 0 to the original and
pan 1 to the transformed version of the pattern. If MIDI ignores that too (I'm not sure, it might depend on the device), then it'll sound the same as
iter will work the same way with MIDI as it does with anything else.
If you run
:t on a function e.g.
:t iter and see it's working on a general kind of pattern type like
Pattern a or
Pattern Num (which would be shown as something like
Num a => Pattern a) then you know it works the same with any kind of pattern. If it's working on
Pattern ControlMap or its alias
ControlPattern then you know it's doing something with controlpatterns like effects, and in that case you might find that it's doing something that the superdirt MIDI implementation or your particular MIDI device might ignore.