Be careful with this. I have some experience with very bad things happening. I don't remember which Simulink versions were involved in that (probably 2015/2016?), and I don't even remember if we tried to load the model into an older or a newer Simulink version.
The problem was that, in comparison blocks (comparing two inputs, and you could set the operator to be one of <, <=, ==, >=, >, != ), the wrong operator was chosen. So, when opened with one (the correct) version of Simulink, the block was a X<Y block, and when opened with the other version of Simulink, the block suddenly became a X==Y block (I don't remember which operators were involved, but you get the idea).
The worst part is that no error or warning message at all was generated.