Is it jitter or buffering delay?
Neither. It's a control cycle duration.
Jitter is a random variation in the period of a nominally perfectly periodic system.
Buffering delay is the delay due to buffering. There's no buffering of data in your case, i.e. your data isn't delayed by buffering.
Don't just use terms you come across! These two would've been easy to google!
and should i need to consider the delay the source node takes in finding the destination node?
You use the word "node", which strongly implies we're talking about a network that is not a trivial graph (i.e. not just a chain, a single cycle or an isolated single device).
This question makes no sense at this layer. You're on the Physical medium access layer. The question is a routing question. I don't think there's a term for what you need aside from "time it takes to find a route", it won't be constant, it depends on the size of your net and the algorithm with which you search.
Also, it's extremely uncommon ina real-world netowrks for a source node to "know" the full route to its target nodes. Instead, it typically figures out the next hop (for example, such nodes can be called "gateway", if they lead to access to a group of non-directly connected nodes), and just sends the frame on its way, and the nodes on the way figure out individual next hops themselves.
This is necessary because in most cases, you're either in a scenario where a) routes aren't static (typical example: the internet), or b) routes shouldn't be transparent to the node, as the overhead of communicating the whole route info would put a great overhead on the system without any benefits (e.g. non-IP-based telephony backhaul systems).