ESPs like MailChimp often make use of their own addresses in the mail-from (from which the domain is used for SPF authentication) in order to do things like processing bouncebacks, rejections, and probably some other returned-mail situations for your campaign. For the most part you probably want them to do this, so you must rely on the other DMARC authentication leg to be able to pass DMARC: DKIM.
In taking this approach, your raw SPF cannot fail - the domain in use for SPF authentication is not yours. The raw SPF result will be a ‘pass’ against servers defined by the SPF record at the servers.mcsv.net location. DMARC-SPF will fail due to misalignment (the SPF auth domain does not match the From: header domain), but as long as you set up DKIM then the traffic will pass on that basis (DMARC-DKIM). Check your dmarcian account to make sure that DMARC reporting shows your MailChimp traffic is completely passing DMARC on the basis of DKIM.
With that set up, the only situation under which messages from the campaign would fail DMARC should be when the target account improperly forwards the message. I suppose you’ll need to assess your target audience to determine the risk there. Once at reject, I expect that 1 campaign would show you the impact on metrics.
A further note on SPF with MailChimp: since they do not use your domain in the MailFrom of messages they send, their entry in your SPF record is completely useless to authenticate SPF. It’s an illegitimate use of SPF. They ask that you put it there to authenticate your use of the domain with them, and some setup cases such as configuration of DKIM on their platform. Check with them, but I believe that once you have those items done, you can remove the entry and save yourself the SPF lookups.