Gen2 Dataflow & Datalake Schemas Issue

Hello Anonymous  and thanks for your comprehensive response. 
To be honest it is the first time using those features and did multiple tests so most of the points above in relation to add/delete columns in the original table in dataflow and those not migrating within the datalake is something that I already concluded during my testing. 
The final part that I don't understand is the same issue that biedw raised in his comment; more detailed steps below:

1) Create a datalake

2) New source in datalake --> DataFlow Gen2

3) Import a table from an excel workbook in SharePoint --> import specific table let's calle it 'Reviewers' with 4 text columns inside.

4) Transform - change column types to 'text'

5) Data Destination as per your printscreens the data lake house and use of the 'Automatic settings' to replace existing table and use of 'Dynamic Schema' 

6) Publish. 

Now my table is under the default .dbo schema and when I refresh the dataflow, it automatically replaces the old data in the table with the new one and works correctly.

As it is a datalake though and I have multiple sources, to organise it better I want to create schemas within the place the tables under those. To do that I am taking the below steps:

1) I am going into the Datalake and create a new schema called 'Schema 1'.

2) Transfer the table that already created before within the 'Schema 1'.

3) Navigate into the existing dataflow and in the data destination to now choose 'existing table'.

4) Make sure that the columns match the existing columns and types (system pre-populates it) and select publish. 

Now in that scenario, the service will return the error that I placed when raised the comment. 

Please be aware that no changes made to the original table (add/remove columns or change type) so we are talking about the same exact table

At last, I did another test in which in the original load in destination (datalake) instead of selecting 'Dynamic' shema I selected the option of a 'Fixed' Schema. I then followed the above steps (publish, move to schema in datalake, assign the table to the schema from the dataflow and refresh the dataflow) and again it return me the same error:

Change_WriteToDataDestination: Mashup Exception Expression Error Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Expression.Error: The value does not support versioning. Details: Reason = Expression.Error;ErrorCode = 10855;Detail = #table({"Title", "Submitted", "Submitter", "Description", "URL", "Meets_Change__criteria_Y/N"}, {});Microsoft.Data.Mashup.Error.Context = User

I hope that makes sense about the specific issue.