It is not something that is trivial that is for sure. That boundary is not really part of this project and more so something the folks working on SwiftUI are more equipped to tackle.
That being said there are some facilities like @State and the view modifier .task that can make async/await concepts like interacting with async sequences work; particularly AsyncChannel fits into this territory as an intermediary type.
This package is focused on the things below that layer; algorithms like zip(_:_:) or debounce(for:...) or types like AsyncChannel. Some of them can help aide in making that boundary better but I don't think it is really in the goals for the AsyncAlgorithms package to offer that UI/model interaction itself.