So, after days of headaches, I finally clarify a lot of how to call native functions of the operating system from a new programming language. The key are static libraries(.lib, on Windows, don't confuse with import libraries which have the same file extension). Dynamic libraries(.dll) won't do the work because:
1.- You could still read the RVA(Relative Virtual Address), from the exported table, but still even if you link the call to the function with such memory address on your binary, that would fail because, that RVA on dynamic libraries are the base address. To get the real address(process of converting RVA to VA(virtual address)) of such function, you need to relocate the RVA at runtime, because its address is shared across multiple binaries, so you would need to call LoadLibrary, FreeLibrary and GetProcAddress, which redirect us to the point 2.
2.- Because that functions are also SO calls, you can't call their RVA, because we will end with the problem of point 1.
So I were in a death point, until I read about Static Linking and Static Libraries. The concept of such kind of libraries is, they don't have RVA, because the VA of its exported functions are resolved at compile-time. But now, I faced another problem, finding information about that kind of file format is hard, and is opaqued by relocation on dynamic libraries, all that I read is by using Dumpbin and the command /SYMBOLS you could create a table of exported functions, but I can't make the users of my language download Visual Studio just for this tool. So, all I wanted to do is reading this by my own, but it's not so easy. First, I tried to read such files from the Dependency Walker, but seems like they don't use DOS Header or PE Header. So I ended up reading about how other languages did this kind of stuff, and I founded that they used a technique called FFI, which, could be described as some kind of Marshallization(it's just my point of view, may is incorrect), but this is not what I want just yet, first, I want to read the fixed VA of the exported functions of such static libraries, but seems like they are missing such information. Any clarification about it?