from unicodedata import name as ᚾᚮᛗᚨ
    ᛊᛈᛚᛁᛏ = str.split

    def ᚢᚾᛒᛂᚺᚱᛂᚮᛊᚨᚾ(ᚥᚮᚱᛑ):
        ᚮᚢᛏ = []
        for ᛍ in ᚥᚮᚱᛑ:
            if 'ᚠ' <= ᛍ <= 'ᛪ':
                ᚾ = ᛊᛈᛚᛁᛏ(ᚾᚮᛗᚨ(ᛍ))[-1]
                ᚮᚢᛏ += [ᚾ]
            else:
                ᚮᚢᛏ += [ᛍ]
        return ᚮᚢᛏ

One would expect it to be possible to #define most of the keywords and functions one would need using the C or C++ preprocessor, though the actual #include and #define macros would still be in Latin script.

Unfortunately, the C standard (Annex D of http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf) does not allow runes in identifier names, but it would work for characters explicitly mentioned in the standard and supported by one's C compiler.

Here's my attempt:

    #include <stdio.h>
    
    #define _ᚠᛟᚱ for
    #define _ᛁᚠ if
    #define _ᛖᛚᛊᛖ else
    #define _ᚱᛖᛏᚢᚱᚾ return
    #define _ᛗᚨᛁᚾ main
    #define _ᛈᚱᛁᚾᛏᚠ(...) printf(__VA_ARGS__)
    #define _ᛊᛏᚱᛚᛖᚾ(...) strlen(__VA_ARGS__)
    typedef int _ᛁᚾᛏ;
    typedef char _ᚲᚺᚨᚱ;
    
    _ᛁᚾᛏ _ᛗᚨᛁᚾ(_ᛁᚾᛏ _ᚨᚱᚷᚲ, ᚲᚺᚨᚱ *_ᚨᚱᚷᛒ)
    {
        _ᛁᚾᛏ _ᛁ;
    
        _ᚠᛟᚱ(_ᛁ = 1; _ᛁ < _ᚨᚱᚷᚲ; _ᛁ++) {
            _ᛁᚠ(_ᛊᛏᚱᛚᛖᚾ(_ᚨᚱᚷᛒ[ᛁ]) & 1) {
                _ᚱᛖᛏᚢᚱᚾ("Hello, %s\n", _ᚨᚱᚷᛒ[_ᛁ]);
            } _ᛖᛚᛊᛖ {
                _ᚱᛖᛏᚢᚱᚾ("Goodbye, %s\n", _ᚨᚱᚷᛒ[_ᛁ]);
            }
        }
    
        _ᚱᛖᛏᚢᚱᚾ 0;
    }

    rune_c.c:16:2: error: non-ASCII characters are not
    allowed outside of literals and identifiers
    _ᛁᚾᛏ _ᛗᚨᛁᚾ(_ᛁᚾᛏ _ᚨᚱᚷᚲ, ᚲᚺᚨᚱ *_ᚨᚱᚷᛒ)
     ^

For other languages, one should be able to use Ruby metaprogramming to make it possible to write Ruby using nothing but runes and punctuation. One would have to define runic methods to replace the functionality def, class, module, and related keywords, but tricks like instance_eval make that possible.

    sub infix:<ᛈ>($ᛣ, $ᛤ) {
        $ᛣ + $ᛤ
    }

    my @ᚠᛁᛒ := 0, 1, * ᛈ * ... *;
    say @ᚠᛁᛒ[100];