Those would both accomplish the same thing, though kickstart would probably let you get way more granular without the need for host profiles. As I understand it, auto-deploy will set the desired state of the new deployments using the host profile, and the final cleanup would be based on the host profile attached to the cluster (and/or via post scripts). Kickstart takes all it's instructions from the KS.CFG that you craft.
Both options would result in a stateful install to disk, and honestly both options would likely benefit from a final PowerCLI cleanup. We use kickstart in my shop and still throw lots of PowerCLI at things to get everything we want. Auto-deploy seems much easier IMO though so I'll definitely be trying to learn more / test more.