Wow, just found this bug as the result of a search for different issue. Quite a big change.
For the scripts that start and stop a service on a single machine, there is a fairly clear substitute in the init.d start and stop scripts; that's fine. For those cases, please state, for the sake of documentation, the actual init.d/* command that substitutes for each of the above removed scripts.
However, a number of those scripts deal with cluster startups, orchestration, or specialized activities. It seems to me those don't map well to init.d functionality. It does not seem right to remove those without providing comparable functionality. If you believe comparable functionality already exists, please state the mapping.
Also, it seems you should get input from experts on the various services before deciding it is okay to whack these scripts that were provided by the developers of those services. Something more pro-active than a jira in the BIGTOP project, opened and committed in a 24-hour timeframe.