warehouse views performance in semantic model

Good day,

I want to know the impact of creating views in a fabric data warehouse when use them in a semantic model. We have the following scenario: We need to make a relationship from a column of a dim table to the fact table in two or more columns, for example a date column in a date-time dimension to invoice date and ship date in the fact table. Fabric only allows a relationship between two tables through one column. To solve this, we are creating views of all the dimension tables that we need to make relationships with two columns. When I add a view to the semantic model, a warning about performance issues appears in the view. We need to create several views from dim tables, and making copy of the data in other tables is not an option for us taking into account storage usage.

Since the views are mostly a select of all columns and maybe in some cases a where with a specific condition, what is the impact in performance of those views in the semantic model?

Thanks in advance.