QTableView / QSortFilterProxyModel Drag/Drop not respecting column/row order of view

Feature Request: Drag and drop within tableViews should replace data according to column/rows order in destination view (i.e. where data is dropped), not according to column/row order of underlying model.

Please refer to the attached project and steps to reproduce the behavior.

The expected behavior is that 

When dragging data, QT only includes information about how the data is
organized, not how it's visualized. If you drag a QTableView that has its
columns swapped and drop it into another QTableView, the drop operation will
result in the columns being applied in an incorrect order from a user's
perspective. 

There is a workaround that you can implement dropMimeData() to define such mappings, but the customer is expecting this to be the default behavior. 

Not sure how feasible is this, so creating this report to get the developer team's view.