After discussing with @cory.quammen, I think the best would be to :
Go forward with a low level rename of the widgets.
Add a simple high-level named wrapper ready to be expanded once vulkan or other implementation are integrated and that can be used by applications, which points, for now, to QVTKOpenGLNativeWidget.
The only low-level rename proposition was then :
QVTKOpenGLNativeWidget -> QVTKOpenGLNativeWidget (no rename)
QVTKOpenGLWidget -> QVTKOpenGLStereoWidget
Let me know if there is a strong opposition to this suggestion.
It should also be noted that QVTKOpenGLNativeWidget has an issue when enabling multisampling, see https://gitlab.kitware.com/vtk/vtk/issues/17154. The problem seems to come from Qt as understood by @utkarshayachit (https://gitlab.kitware.com/vtk/vtk/issues/17154#note_546700). Because of this, I’m using mostly QVTKOpenGLWidget in my own applications, which does not suffer from this issue. So personally, I’m not particularly in favor of renaming this widget by adding a “Stereo” label to it, since I don’t use QVTKOpenGLWidget for its stereo capabilities at all. But I agree that for the other widget, the “Native” term is not very clear.