Understand, I am approaching this in a completely one sided way -- it will not matter to the person using the language whether you call it a function or a method or a subroutine (at least, it should not). I have *absolutely* no knowledge of how all this is going to be implemented. I'm a complete ignoramus there.
So, if you think it will be just as much work in the implementation to have functions and methods as it would be to just use methods, fine. But if it is going to be *more*, then I think you will have to justify the apparent redundancy -- and style is not a valid excuse.
Using a purified OO model (all method) will undeniably reduce the syntax. That too is "just style" UNLESS it will also reduce the whole code base of the project, which was my original motive for the suggestion. But I admit my naivete; I have no real evidence that that would be the case.