As the change wrangler, I am in favour of finding a way to centralise feedback on changes when they are announced to make it easier for everyone to keep up with the conversation. (It would also reduce my workload by only needing to post the change in one place - so yay, a little less work for me 
)
My 2c is is that the change process is the mechanism/process that FESCo uses to manage each Fedora Linux release. That is a big task, and if the current process is making that difficult for FESCo members to do, then I am glad we are looking at changes to make this easier.
I would like to resuggest @bcotton’s suggestion he made on the devel-list: use the email lists for the announce and discussion, and post one post linking changes announced on discourse highlighting that the changes are live. This could be a potential middle ground. I also lean to batch-posting changes, so this means there would be one post every week/every few days containing the current changes announced, their summaries and links to their posts on the devel-list.
I do like @bookwar 's suggestion in point 1, but Im not convinced the changes process should be included as a way to get new contributors to the project. I feel like someone proposing a change to Fedora Linux is already part of the project for a time, so maybe its a way to retain contributors? I dunno, thats a topic for another thread in any case