Problem/Motivation
Per #3181793, there is at least one site that is using signup forms as a part of subscription-update UX. Users may return to a signup form, enter an email address that is already subscribed to the list in question, and then select interests to join subgroups and receive the relevant mail. This much is already supported by the existing code.
However, there is one gotcha--the user may not assume that leaving a given checkbox is the same as requesting to opt out of that subgroup. It's the classic problem of trying to represent a three-state setting (leave, join, do nothing) with a binary interface. The initial solution was to provide an admin config option to choose between "always add" behavior and the status quo.
Proposed resolution
It would be possible to make an ajax call to the Mailchimp API when the user blurs focus on the email field, check to see if that address is already subscribed to the list, and if so, populate the subgroup checkboxes according to the preferences they set in the past. This could provide convenience and also help prevent unintended duplicate submissions. However, it introduces obvious complexity: an added network call, a race condition between the user checking a box and then having javascript update it, and a non-obvious behavior for users who expect static signup forms.
The maintenance team has not decided on whether to move forward with this feature, which would carry both benefits and drawbacks. If you have an opinion, please feel free to influence our decision.