Re:CM12 "Rerun behavior" equivalent??
That's correct. This is because applications are enforced differently on client systems. Similar to updates, applications define a desired state for that application if it is required: either installed or uninstalled. The client agent then goes about enforcing that state starting at the deadline time specified in the deployment. Then, every time the deployment evaluation cycle runs, the client will ensure that state is still enforced (based upon the detection logic) and if not enforce it. This is an intent based system where you simply define what you want to happen and then ConfigMgr does it. The key here is that Applications are called "Applications" for a reason: they are meant to install applications because that's really the only time this intent based model makes sense.
For recurring tasks like scripts or what you have defined above that do not truly have anything to do with the state of the target system, packages and programs are still the primary method to use. Packages and programs are not going anywhere -- not sure how you came to that conclusion -- they are still very much needed for these scenarios.