The relevant line (where the channel is configured) is
here. In the past when people have needed NI DAQ customisation, the easiest solution has just been to hack in an if statement at this point catching a specific MAX_name and channel, and configuring that one differently. Would be great to have it officially supported though. I think the biggest blocker to that is
labscript#49, as there is no easy way to store per channel configuration options (output/input channel "device_properties") in the HDF5 file. There are workarounds of course (like manually storing channel configuration in the parent device group, or abusing the "connection_table_properties" storage), but it would be good to decide on a proper structure for storing them before adding other features that rely on it (which thinking about it is probably just a JSON encoded dictionary, keyed by channel name, stored as an HDF5 attribute of the group for the parent device)