Nope, because CSRF only applies to hijacking an authenticated session from an unauthenticated page. For example, without knowing a Marketo user's username and password, being able to trigger Marketo campaigns because you got them to go to your malicious site. (Note any worried lurkers: this is not possible! I'm describing the potential case that CSRF tokens are there to block.)
In this case Alex is talking about a Marketo LP (thus unauthenticated) posting data to an external service (perhaps expecting an API key, but if the end user is not to be prompted to enter the key, it must be embedded in the page where anyone can copy it). If it were possible to require a popup w/interactive authentication to the external service (not publishing the credentials to the world) that would be a different story.
You can cobble together pseudo-authentication for a Marketo form post using the Marketo Unique Code (blog post on that in the future). However, it doesn't happen interactively, it's something for the back end and could potentially take minutes to process under load. Similarly, you could use any custom field as a password-like (or password-lite!) field, so only if a certain field supplied by the end user matched this other (non-updateable) field would you continue processing. But that processing is still server-side, like via a webhook. And in both of the cases, the person has to enter something they know in advance, it's not a regular lead gen form post.
.png)