The unlit redstone torch is still lit even on setblock command

Immediately after being placed, the torch is unlit. You can see that if you pause the video at that point. However, for a redstone torch to remain unlit, it needs to be activated by a redstone signal, which is not happening in your videos.

If you have official information that this should behave differently, please provide a source.

This report has been temporarily closed as Awaiting Response. It will automatically reopen when you comment with new information. Please be sure to provide all requested information. Reports that do not contain enough information may be closed as Incomplete.

I meant if I setblock the unlit redstone torch, it should be remain unlit. But what happened was it got light it up itself. 

I have a picture that there is 2 kinds of redstone torch in setblock command.

The first video was that the redstone torch in setblock command is all good.

The second video was the unlit redstone torch in setblock has its problem. It got unlit for a miliseconds then got lit up for the rest of the time. It should remain unlit for unlit redstone torch.

The item and block are just "redstone torch". There is no difference between a lit torch and an unlit one at the inventory or gameplay level, only at the technical implementation level. So while you can place either one with a command, it immediately becomes part of the world and subject to the rules of world simulation that all gameplay follows.

If the torch didn't turn on in this situation, it would behave differently from any redstone torch you could obtain any other way. That is, it would be a new kind of redstone torch, one that doesn't follow the rules for world simulation. In effect, what you're asking for is a new kind of block and item, which makes this a feature request.

Except that you can do it with other things, putting them in "invalid states", such as blocks that normally need support.
That's especially prominent in java, but this also plagues that edition (see related report, marked as Won't Fix), so no, this is not a feature request.