It would be useful to have this option available for strmxor, preferably as default "on".
This way tiled and non-tiled xor should generate the same number and shapes of results.
The only expected result differences would caused by non-orthogonal polygons overlapping tile boundaries in a way that the cut points don't fall on database units.