When setting a custom vtkLookUpTable (i.e. for using a colormap), the mitkImageVtkMapper2D automatically overwrites the range of the lookuptable.
Possible fix: Check if there is a property for vtkLookUpTable. If yes, do not modify the range of the lookuptable.
apparently a vtkLoopUpTable is set automatically so the property as such cannot be used to handle custom vtkLookUpTables
Workaround would be to have another property "customvtklookuptable" or likewise. On the other hand the question arises if it is the best solution to change the range
Could be solved by @kislinsk suggestion to change rendering mode to LOOKUPTABLE_COLOR to not envoke the levelwindow to overwrite the range