No!
The C99 standard says (section 6.10.2):
A preprocessing directive of the form
# include pp-tokens new-line
(that does not match one of the two previous forms) is permitted. The preprocessing
tokens after include in the directive are processed just as in normal text. (Each
identifier currently defined as a macro name is replaced by its replacement list of
preprocessing tokens.) The directive resulting after all replacements shall match one of
the two previous forms.
However, there is another rule (section 10.6.3.2, on 'The # Operator') which says:
Each # preprocessing token in the replacement list for a function-like macro shall be
followed by a parameter as the next preprocessing token in the replacement list.
The '#include s' in the macro expansion fails this constraint - the word 'include' is not a parameter to the macro-like function.
This prevents you from generating a (usable) '#include' directive. In any case, during macro expansion, there is another rule (section 10.6.3.4) which says:
The resulting completely macro-replaced preprocessing token sequence is not processed
as a preprocessing directive even if it resembles one.
This means that you cannot generate any preprocessor directive from the result of a macro expansion.
Your effort is, sadly, doomed to failure.