Yes, you have to add and map additional Segment traits to represent the unsubscribe-related fields.
However: you should be aware that you're probably opening a DoS attack vulnerability against your Marketo API call limit using such methods. Anything that allows an end user to consume an API call for an untrusted action creates such a vuln.
I would recommend you rethink your way of managing unsubscribes to push this information directly to Marketo using the Forms JS API.
I connected customer.io as source and marketo as distance to segment.io. So I see success pushing from customer.io to segment.io, but data requests from segment.io to marketo are failed. Can you help me with marketo config for that action?