No, SE-0328 is purely to lift the restriction that opaque types can only appear as the top-level result type. It does not add the ability to express constraints on associated types. That said, we absolutely want this syntax to work with opaque types, but we feel like it belongs in a separate proposal. If the community feels differently, that's valuable feedback.
You're right - this pitch is part of an effort to make generic programming in Swift more approachable. I posted a discussion with higher-level goals and directions here. This is also a step toward the vision that was laid out in Improving the UI of Generics, but focusing on the aspects that design guidance and progressive disclosure into the generic programming experience (contrasted with fully generalizing some of the generic programming features that are rather limited today).