@bflad I think my provider migration issue with state drift may be related to this semantic equivalence issue. It feels like the custom type may be the way to solve the issue but I need to read the doc and understand it better first.
My issue occurs for both SetAttribute and StringAttribute where the first one is optional and computed, and the second one is computed only.