This would require an API change, though, since "loose" is already in `make_inverse_operator`, right?

Incidentally, the way the C code works, you can make one forward solution, and use it for both loose and fixed orientations (all the forward conversion calls are handled in the inverse calculation routines), so the proposed behavior is at least consistent with that...