Yeah, I kind of anticipated this one and probaly should have created a note in the changelog.
This is a cosmetic thing. LTN doesn't have a control to make stations just provider or just requester. They are alway both. You can effectively disable the ability of a station to provide or request things by assigning a really high threshold, and that is what is done when you disable the Requester or Provider service in 2.0 version of the combinator.
The previous version only inferred Requester or Provider by the presence of negative item signal or a high provider threshold threshold. If you did not have a negative item / fluid signal or there was a high provider signal the combinator would display as a provider. In reality, simply adding a negative signal would have resulted in both provider and requester being checked the next time you opened it. This led to lots of confusion (as well as feature requests) all stemming from the fact that LTN does not have distinct provider and requester stations.
The changes I made in 2.0 will take a little adjustment in thinking, but provide a more accurate representation of how the station is configured (actuall control signals) and some additional utility by being able to enable and disable the "service" without loosing threshold settings.
That said, I will add a command to uncheck "Requester" on combinators without negative signals.
