But in H8 there are 3 candles, one for 00:00, one for 08:00 and one for 16:00. Your "Hours filter" is between 22:00 and 23:00. If Open prices only works on the open prices only, there are only 3 "ticks" for the day - at 00:00, 08:00 and 16:00. No tick comes after 16:00.
Check if the EA modified the stop itself. First, the EA calculates the future stops and sends them to the server as absolute values. If the SL should be at 1.2345, that value is sent to the server, not something like 5 pips. But I programmed it to correct the stop if slippage occurs. The problem is that sometimes the trade is opened at price that is different than the requested price (slippage), but SL and TP remain at the requested levels - as a result the open price is shifted towards SL or TP a little bit. So I programmed the EA to modify the stops if that happens, so that if you wanted to have for example SL at 10 pips relative to the open price, to be 10 pips and not 8 pips for example. Take a look at the logs for such "modify" action right after the trade is opened, maybe this can explain the confusion.
In Value -> Time you have the option to "shift" the time forward or backwards
"For each Trade" passes as many times as many Sell trades there are. If you have 3 Sell trades, the block will pass 3 times, once for each of them. Unless you set some limits in the settings.
"once per trade/order" uses temporary memory and when you restart the EA, that memory is reset and the block would pass again once for each trade.
But what are you trying to do? I have this feeling that you want to do something like "Add to Volume (every 10 pips)" in the examples (https://fxdreema.com/examples)
When let's say "Buy now" runs, it uses the current Ask price to say to the server where to put the future trade. But until the request reaches the server, there is some time... let's call it network time. If the market is fast, the current Ask and Bid prices could change quickly and the broker opens the trade at the Ask price that is actual and could be different than what you requested. This is slippage.
There is a parameter for "slippage" in OrderSend(), which was the maximum slippage that you allow for the trade, but I think that this parameter no longer works for most brokers. And they will open the trade with whatever slippage. I don't know more details to be honest, and I don't know how to tell the broker to not open the trade if the price changes too much 
I know this bug, it is just a visual bug. That input sits there all the time, but it goes visible when it doesn't need to. But "cross width" is something that nobody uses anyway. I know only 1 case when someone really needed it, and it was years ago. Don't be afraid of it, it doesn't break anything.
You wrote "test" as a name of the window where the data from "Comment" will be written. Normally there is no such window and the data goes nowhere
You want such list in the EA input properties? I know that anyone can create enumeration that will appear there as a drop-down, but then only 1 value can be selected, not multiple.
Desktop or web version? Because in the web version these results are also Variables, so you can print them let's say in the "Comment" block
No, I personally don't like advertisements of any kind and I can't force myself to think about this, it's too complicated for me
I see you wrote some dots at the end of each symbol name, which is something... interesting... and potentially could be the problem. Do you have errors in the logs?
Can you tell which block doesn't work? If you put Draw arrow after any block, you can detect whether it worked or not. Also do you have some error messages?
By the way, by default MarketCloseSwitch is set to "false", also try to see if you really changed it to "true", otherwise I don't see how block 79 can be reached.
Which of your EAs is this? Otherwise this number is also known as EMPTY_VALUE and I can guess that at the time when you print it, no trades are loaded.
Are you talking about slippage?
What do you have in the logs?
Oh yes, there was some problem when you have a constant/variable named like "Timeframe", because there is a parameter with the same name already (that Timeframe below Symbol). It's some weird problem that I have to somehow fix, but I'm also scared to touch this part of fxDreema, because I can easily broke something else
You can see the current time in seconds since 1.1.1970 here: https://www.epochconverter.com/
So yes, the time is measured in seconds since that day. It appears as seconds, because Value -> Numeric has "double" time, which is floating number, and the value is treated as a number. Value -> Time has "datetime" type and the EA knows to format it a little bit. Any "datetime" variable is integer on a lower level.
Of course the easiest is to add just one parameter where the people could write only 1 number. But after time someone will ask me for the ability to define period of time, starting from... let's say 00:00 of the current day and ending 20 minutes before the current time. Or even using absolute dates, like the first day of the month, or something else fancy
Try it. I never tried to remember those hours