It posts and that's all. The response is just ok, with no message timestamp, so you can't thread a follow-up onto it, edit it later, or delete it. If you need any of those, post with chat.postMessage and a bot token instead. It returns the timestamp. Our Slack API page covers that route.
Buttons need a server behind them. You can include Block Kit buttons in a webhook message, but a click is sent to the app's interactivity Request URL. Without something listening there, the button does nothing. At that point you're building a full app anyway.
One channel per URL, one message a second. Slack limits incoming webhooks to about one message per second, with short bursts allowed. A script that posts 200 rows in a loop gets throttled, and anything you didn't retry is gone. Sending to ten channels means ten URLs, and your code has to know which is which.
Nothing tells you a message didn't arrive. Slack doesn't retry for you. If your sender ignores the response, a failed alert just never shows up, and nobody notices until the day it mattered. If the tool sending the alert already has its own Slack app, use that. It usually handles retries better than a hand-rolled webhook.