> OK, so taking the danger of changing hot paths through different inputs> into account, do you think that it might be a promising idea to mix> instructions from several paths?

Yes, this idea has been explored simply and empirically by some trace
scheduling techniques. What we are missing is a good theoretical work on it.

Almost all the trace scheduling are simple heuristics that are
experimented on some toy benchmarks with fixed data input. The problem
of mixing instructions from several paths is still open since nobody
demonstrates that the performances are good on multiple data inputs
(from the theoretical and empirical perspective).

This would possibly help the scheduler> to reorder instructions such that the pipelines/functional units are> maximally exploited but on the other hand no particular path is favored/> neglected too heavily.>

Yes you are right. But new problems will arise regarding instruction
cache effects...
Anyway, providing an instruction scheduling method for multiple data
paths is a promising idea if you can bring some theoretical knowledge.