You can do what you discuss above.

The bigger question remains can FSBP place pending orders?

FSB Pro uses pending orders internally when the entry indicators has two entry prices. Examples: Bollinger Bands, Price Move, Pivot Pints... You don't see the Pending Orders placed in MetaTrader because the experts keeps them internally and trade with market orders when the exact trading price is reached. This is done to reduce the MetaTrader's traffic and latency.

I noticed this behavior as well, but I can tell you that order execution is faster with pending orders once their price is hit, as they already reside on the broker's server and are triggered there with 0 latency. If you do it with market orders, price first has to travel to you (few ms latency), EA has to check if the order needs to be placed (another few ms latency), then send the order to the broker (and more ms latency again). Market orders are always the slowest type of order execution because of the above explanation. Pending orders, on the other hand, reside directly within the broker's server already and are triggered much, much faster. How do I know this? I do work part-time for a well-known broker on their backend (MT4 bridge to their liquidity providers). Market orders always have a higher execution time (and hence more slippage) by a magnitude of about 10! Pending orders are filled within ~30ms, while market orders are filled within ~300ms. You should really consider making FSB use pending orders.

FSB Pro uses pending orders internally when the entry indicators has two entry prices. Examples: Bollinger Bands, Price Move, Pivot Pints... You don't see the Pending Orders placed in MetaTrader because the experts keeps them internally and trade with market orders when the exact trading price is reached. This is done to reduce the MetaTrader's traffic and latency.

Is this not what a support and resistance line is?

Seems like we are sweating the simple stuff here.

We would then create pending orders which is then taken at within certain pips when price moves over S&R

The bigger question remains can FSBP place pending orders?

indicator takes swing high/lows values from Zigzag

Be careful with the ZigZag indicator. It repaints the history and shows highly overestimated results. All indicators that use ZigZag (Fibonacci, Support & Resistance, ...) are potentially dangerous also. 
I've heard for a none-repainting ZigZag, but I've never seen one working.

I should show you mine, I guess it must be in my old computer, maybe I can locate it. Non-repainting zigzag, but the main problem with it was lag. Other versions exist also, which are non-repainting or non-recalculating, i believe they use user-defined leg length, hence if that length is reached, the leg gets drawn without recalculation.

indicator takes swing high/lows values from Zigzag

Be careful with the ZigZag indicator. It repaints the history and shows highly overestimated results. All indicators that use ZigZag (Fibonacci, Support & Resistance, ...) are potentially dangerous also. 
I've heard for a none-repainting ZigZag, but I've never seen one working.

How I can remember that indicator takes swing high/lows values from Zigzag indicator and extends a little bit to get zone with "base" candles.

The first hurdle would be to determine how S&R levels are selected.

The second would be how those levels would actually be implemented to simulate how manual traders use them.

Well, basically and principally everything is possible. Regarding FSB, a very good understanding of how it has to be coded is needed, otherwise one can see many holy grails in backtesting only to find out that the indicator has critical errors. I think most who have done indis for FSB have experienced it at first. One cannot forget some limitations of FSB, it's important to keep things light calculation-wise.

In conclusion, yeah, it's possible, but the devil is in the details (like with most things).

The d/l link for the latter is:
https://www.fxtradingrevolution.com/upl … s_2.98.ex4

EAs cannot interact with either of them.

It's not these actual indicators with which I'm concerned; it's the viability of developing something similar into a usable indicator. Perhaps the ideas behind them are feasible, but not well-executed. (Don't know, as I haven't used them.)