DeployStudio and Catalina?

DS is dead, man. Time to move on.

Even if machines are not DEP enabled, it is easy enough to have a provisioning script in a policy run via enrollment trigger in order to "image" them. Have a dummy file placed via touch for machines that have already run the provisioning script, that way if they ever get re-enrolled, they don't go through the script again. For example:

#!/bin/bash

# Check if script has run before, and if so, exit program
if [ -f "/Library/Preferences/dummyfile.plist" ]; then
echo "script has already run once. Exiting."
exit 0
else
#run whatever you need to run here
#Create temp file to signal script was run once before
touch /Library/Preferences/dummyfile.plist
fi
exit 0

You can get pretty fancy with this, using different dummy files for different things, even utilizing the API to add a machine to certain groups based on the presence of a certain file. Utilizing something like this means there is literally no need for DeployStudio anymore. To get macOS on a machine, use Internet Recovery or install it from a policy (you can do an erase and install using one click in self service). Check this article out.

What's easier? Running an eraseinstall on a group of Macs, walking through setup assistant, double clicking an enrollment.command file, approving the MDM profile, and walking away? Or banging your head against the wall trying to make tools made for other operating systems and other file systems work for the new one, and even if you get it working they'll only work until next year?